Skyport: Assigning Workspace to a user
what is the best way to assign a user to a workspace
I am a Clear-Com dealer and a end user requests a GEN-IC instance (managed service)
We are account admins for the Skyport account
we create a workspace for End User
we purchase a PREMIUM GEN-IC instance
we move the instance to the workspace
we invite the End User as a GEN-IC admin (we do this, so we still maintain access the workspace, because we are offering a managed service)
GEN-IC admin access the workspace and invites other people (virtual clients )
A few weeks later the Gen-IC admin then requests to add their own (customer-owned) LQ to the workspace
We then attempt to promote the GEN-IC admin to become a workspace admin
At this point , we are not able to do it and the customer does not have privileges to add a LQ to the workspace
??? we thought GEN-IC admins can now add link LQs to their GEN-IC subscriptions ??
??? why can't we promote or revoke and re-invite the GEN-IC admin to become a workspace admin and we remain account admins for the workspace
Answer:
The best workflow from an account owner/admin POV
create the workspace
add workspace owner* to the EMPTY workspace
purchase Gen-IC instance
move GEN-IC instance into workspace
workspace owner can then create admins, and virtual clients and add LQs
*it important to invite / add the workspace owner FIRST , whilst the workspace is EMPTY
Registering On-Premises Devices (LQ)
Introduction
SkyPort allows registering on-premises LQ devices and linking them with a Gen-IC. The following rules apply:
Rules
Account owner/admin can add remove their own LQ and workspace owner/admin cannot remove a LQ that was added by account owner/admin.
Workspace owner/admin can add remove their own LQ and account owner/admin cannot remove a LQ that was added by workspace owner/admin.
Gen-IC admin/virtual client users can’t add a LQ.
At least one active Premium subscription must exist on the account.
If the final Premium subscription is removed, all LQ devices are disassociated from the account.
a. The LQ device itself is not automatically notified and may still appear “registered” locally, but attempts to communicate with SkyPort will fail