User management in CloudStudio has two layers:Documentation Index
Fetch the complete documentation index at: https://docs.cloudstud.io/llms.txt
Use this file to discover all available pages before exploring further.
- Workspace membership — who can sign in to your workspace at all, and at what role
- Project membership — which specific projects a workspace member can see
Workspace roles
| Role | Can do |
|---|---|
| Owner | Everything an Admin can do, plus billing access and ability to add/remove other Owners |
| Admin | Invite users, create projects, assign users to projects, view usage, manage storage quotas |
| Member | Work inside projects they’re assigned to. Cannot manage other users or settings. |
Inviting users
From Workspace settings → Users:Enter the user's email
Use their work email — CloudStudio enforces this for audit-trail consistency.
Optionally assign to projects
You can select projects right here, or do it later from the project page.
SSO / SAML
CloudStudio supports SAML 2.0 with any IdP (Okta, Google Workspace, Microsoft Entra, Auth0, etc.). When SAML is configured for your workspace:- New users are JIT-provisioned on first login — they don’t need a separate invitation
- Their workspace role is determined by IdP group mapping
- Sessions are managed by the IdP — when you deactivate someone in your IdP, they lose CloudStudio access immediately
- The CloudStudio password login is disabled for SAML-managed users (you can keep a small allowlist of password-login admins for break-glass scenarios)
Project access
Inviting someone to the workspace doesn’t give them access to any specific project. You assign per-project:- Open the project
- Project settings → Members → Add
- Pick users from your workspace
- They see the project in their CloudStudio menu within a few minutes
What pool access follows from project access
CloudStudio derives storage access automatically:- Being a project member grants access to that project’s storage pools
- The CloudStudio menu-bar app on the workstation only mounts pools the user has rights to
- Adding or removing project members updates mount lists on the next login (or within ~15 minutes for active sessions)
Removing access
To remove someone:- From a single project
- From the workspace entirely
- From the SSO side
Project settings → Members → click the row → Remove. They lose access to that project’s storage on next login.
Audit log
Workspace owners can view an audit log of:- User invitations and removals
- Role changes
- Project membership changes
- SSO configuration changes
Common patterns
Onboarding a new editor
Onboarding a new editor
- Invite as Member with their work email
- Assign to the projects they’re working on
- Send them a link to Quick start and Connecting to your workstation
- Have them connect to their assigned workstation while you’re on a call so you can debug if anything’s odd
Bringing on a freelancer for one show
Bringing on a freelancer for one show
- Invite as Member
- Assign to that single project only
- When the show wraps: remove from the project. Keep the workspace seat dormant for ~30 days in case of pickups, then remove from the workspace.
Promoting an editor to lead
Promoting an editor to lead
Just elevate their workspace role to Admin so they can invite users and create projects themselves. Project memberships are unchanged.
Splitting access between a producer and an outside agency
Splitting access between a producer and an outside agency
Two paths:
- Same workspace, different projects: invite the agency as Members, assign only to the agency-relevant projects.
- Separate workspaces: for cleaner isolation, run two workspaces under your org. Contact your CloudStudio account rep — switching to multi-workspace billing is straightforward.
What’s next
- Storage tiers & quotas — what storage your team gets access to
- Billing & invoices — how user count affects billing (it doesn’t — billing is storage and workstation based)