Documentation

Admin Relationships


The Admin Relationships page in MSPControl is used to manage delegated administrative relationships for the current organization. This page helps administrators create new admin relationships, review whether they are active or terminated, monitor compliance state, and perform follow-up actions such as sending approval reminders, copying invitation links, terminating relationships, or deleting records.

This section is especially important for organizations that use delegated administration models such as GDAP. Instead of tracking relationship lifecycle outside the platform, MSPControl provides a dedicated page where relationship status, approval workflow, and operational actions can be managed in one place.


Table of Contents


Admin Relationships Overview

The Admin Relationships page acts as the central list of delegated admin relationships for the organization. Each row represents one relationship record and shows its lifecycle state, start and end dates, and compliance state. This makes the page useful not only for setup, but also for ongoing review of delegated access over time.

Because delegated admin relationships often affect tenant access and customer approval flow, this page should be treated as an important governance and operational management area. It helps administrators confirm which relationships are still active, which ones have expired or been terminated, and which actions are still available for each entry.


Admin Relationships List Page

The main Admin Relationships page displays relationship records in a table. The list provides a quick operational overview and allows administrators to create a new relationship, filter the view, refresh the current data set, and perform row-level actions against existing records.

The page is especially useful when administrators need to monitor relationship lifecycle across several records or quickly identify which relationship still requires action, approval follow-up, or termination.


Admin Relationships Page Controls

  1. Create Admin Relationship opens the dialog used to create a new admin relationship.
  2. Only Active limits the list to active relationships only. This is useful when administrators want to review only currently valid delegated access.
  3. Only Created in Control Panel limits the list to relationships created from MSPControl itself. This helps distinguish platform-created records from other possible relationship sources.
  4. Only Policy Not-Compliant limits the list to relationships that are not compliant with the expected policy state.
  5. Refresh reloads the current relationship list. This is useful after creation, approval actions, or lifecycle changes.
  6. Category Filter allows administrators to narrow the visible results using the available dropdown options.
  7. Search helps locate a relationship by name or other searchable values.
  8. Column Visibility allows administrators to control which columns are visible in the table.
  9. Page Size Selector controls how many rows are shown at one time.

Admin Relationships Table Columns

  1. Admin Relationship Name shows the relationship identifier or visible name.
  2. Status shows the current lifecycle state of the relationship, such as Active or Terminated.
  3. Start Date shows when the relationship became effective.
  4. End Date shows when the relationship expires or ended.
  5. Compliance Status shows whether the relationship is compliant with the expected policy state.
  6. Actions provides the row-level controls used to manage the relationship lifecycle and approval flow.

This table is helpful because it combines lifecycle timing and compliance visibility in one place, making delegated access easier to review during audits or operational checks.


Create Admin Relationship

When administrators click Create Admin Relationship, MSPControl opens the creation dialog. This workflow is used to start a new delegated admin relationship based on a predefined policy.


Create Admin Relationship Fields

  1. Select Policy allows the administrator to choose the policy that should be used for the new relationship. In the example shown, options such as Default GDAP Policy and Read-only GDAP Policy are available.

This is important because the selected policy defines the relationship model that will be requested. A broader policy such as a default GDAP policy may grant a wider operational scope, while a read-only policy is better suited for lower-risk review or monitoring scenarios.


Create Admin Relationship Usage

The creation dialog makes it clear that MSPControl is using policy-driven delegated admin relationships rather than forcing administrators to build every request manually. That helps standardize relationship creation and makes delegated access easier to control over time.

By choosing from predefined policies, administrators can align new relationships with existing operational models and avoid inconsistent access requests across customers or hosted organizations.


Admin Relationship Actions

Each relationship row contains several action icons. Based on the provided screenshots and tooltips, these actions include:

  1. Make Admin Relationship request starts or sends the relationship request workflow.
  2. Terminate Admin Relationship ends the delegated admin relationship.
  3. Send Customer Approval invitation reminder Email sends a reminder email to the customer so they can complete the approval process.
  4. Copy Approval invitation link to Clipboard copies the approval invitation link for manual sharing or follow-up.
  5. Delete Relationship removes the relationship record from the list.

These actions are especially useful because delegated admin relationships are not just static records. They move through a lifecycle that may require request creation, customer follow-up, compliance review, termination, and final cleanup.


Understanding Relationship Lifecycle

The screenshots show both Active and Terminated statuses, which indicates that the page tracks relationship lifecycle over time rather than only current access. This is useful for historical review and for verifying that expired or ended relationships are no longer treated as active delegated access.

The presence of approval reminder and approval-link actions also shows that customer participation is part of the workflow. In other words, creating the relationship record alone is not always enough. The relationship may still require customer approval before it becomes fully effective.


Compliance Status

The Compliance Status column is important because it helps administrators see whether the relationship matches the expected policy state. This is especially useful when the platform is being used to enforce standardized delegated admin models and not every relationship should remain valid indefinitely or outside policy scope.

The Only Policy Not-Compliant filter makes this even more useful, because it allows administrators to focus directly on relationships that need attention instead of reviewing the full list manually.


How Admin Relationships Fit into MSPControl

The Admin Relationships page gives MSPControl a dedicated place for managing delegated admin access lifecycle. Instead of handling relationship creation, customer approval follow-up, compliance review, and termination in disconnected systems, administrators can work through the full relationship workflow inside one page.

This makes the page useful for governance, operational access control, and lifecycle management. It supports both day-to-day access administration and periodic review of whether delegated access is still valid and policy-aligned.


Best Practices

  • Use predefined policies carefully when creating a new admin relationship so the requested access level matches the real operational need.
  • Prefer more restrictive policies, such as read-only access, when full delegated administration is not required.
  • Review Status, End Date, and Compliance Status together when checking whether a relationship should remain active.
  • Use Only Active for current-access review and Only Policy Not-Compliant when focusing on governance exceptions.
  • Use the approval reminder and clipboard-link actions when customer approval is delayed, instead of creating duplicate requests.
  • Terminate relationships promptly when delegated access is no longer required.
  • Delete relationship records only when cleanup is appropriate and the historical record is no longer needed in MSPControl.
  • Refresh the list after request, approval, or termination actions so the displayed lifecycle state remains current.