Manage server subusers
A subuser receives selected permissions on one specific server. This access is independent of any organization or project.
Audience, availability, and prerequisites
Section titled “Audience, availability, and prerequisites”This guide is for server owners at cloud.8labs.id. Only the server owner and platform root admins can manage subusers. Organization admin status or settings.manage alone does not grant subuser management.
The Settings → Access controls must be available in the hosted service. The collaborator must already have a runtime account. Confirm their account email and the minimum permissions needed before continuing.
Compare subusers and projects
Section titled “Compare subusers and projects”| Method | Scope | Where to manage it |
|---|---|---|
| Subuser | One server | Server Settings → Access |
| Project member | Every server in a project | Folder Share dialog |
Both use the same permission set. Effective access is the union of all applicable sources.
Choose a subuser when one server is enough. Choose a project when the same collaborator needs access across a server group.
Add a subuser
Section titled “Add a subuser”- Open the intended server.
- Open Settings → Access.
- Choose the add action and enter the collaborator’s existing account email.
- Select only the required permissions in the picker.
- Submit and wait for the updated subuser list.
- Ask the collaborator to open the server with their own account.
Do not add the server owner as a subuser. The owner already has full access and cannot be added to their own server.
If the person has no account, direct subuser creation cannot register them. Use a project invitation, where available, or contact support about onboarding.
Edit or remove a subuser
Section titled “Edit or remove a subuser”- Open Settings → Access on the same server.
- Edit the existing subuser’s permissions and save, or choose the remove action.
- Wait for the updated list or confirmation before leaving the page.
- Review the person’s remaining access sources if the aim is complete removal.
Removing a subuser removes that direct grant only. Project membership, organization owner/admin status, or server ownership can still provide access.
An existing browser page may need to reload to display the changed controls. Do not treat an old open page as evidence that a grant still exists.
Safety and troubleshooting
Section titled “Safety and troubleshooting”- Access controls are missing: confirm you are the server owner. Ask the owner to make the change; do not share their credentials.
- Account not found: verify the runtime email. A billing account alone does not establish runtime account availability.
- Required action is unavailable: compare the intended action with the saved permissions, then inspect other relevant grants.
- Access remains after removal: check the combined access model, rather than repeatedly removing the same row.
Console, power, restore, and reinstall access can affect running workloads or data. Grant each deliberately. For suspected misuse, remove the relevant grants and contact the server owner or support. Include the server identifier and time, without credentials or sensitive console output.