MSP global view
Can a grandparent MSP parent (channel) workspace start subscriptions for grandchild customer workspaces?
Yes, Managed Service Provider (MSP) administrators and admin users with sufficient permissions start, stop, and edit workspace subscriptions for their assigned parent (channel) workspace and all its descendant workspaces, including both child and grandchild workspaces.
For further information, see Workspaces.
How can I identify the root MSP workspace that an MSP admin user has permissions for?
From Global view, go to Workspaces. The Name column displays the root MSP workspace for each MSP admin user.
For further information, see Adding a new MSP admin user.
Can a user account added as an MSP admin user also be added as an admin user to descendant child workspaces?
Coro recommends not to add an MSP admin user account as an admin user to descendant child workspaces because this can create the following MSP roles and permissions conflicts:
- The admin user roles and permissions override the MSP admin user roles and permissions.
- Removing the admin user reverts roles and permissions to the MSP admin user.
However, you can add an MSP admin user account as an admin user after creating the child workspace.
Can MSP admin users independently select Coro bundles and modules for their customers?
Yes, MSP admin users can add bundles and modules directly from Global view > Workspaces without requiring support from a Coro employee.
Why were MSP admin users removed from my child workspaces after the release of Coro v3.2?
With the release of Coro v3.2, Coro introduced MSP roles and permissions management, allowing for more granular control over Managed Service Provider (MSP) permissions. When you create an MSP admin user in the Global view, they automatically receive permissions for all descendent workspaces, eliminating the need to update the same MSP admin user at all levels.