Users & Roles¶
CloudVerse AI uses role-based access control (RBAC) to determine what each user can see and do. Access is configured in Organization > Overview.
Open Organization Overview¶
Go to Organization > Overview from product navigation.
Tabs¶
| Tab | Use it to |
|---|---|
| Overview | See a summary of users, roles, and access configuration |
| Users | Invite users, assign roles, and configure Perspective scopes |
| Roles | View built-in roles and create or manage custom roles |
| Teams | Group users for inherited access (if enabled) |
| Workspaces | Organize resources and teams into access boundaries |
| Business Scopes | Define reusable business scopes for access objects |
| SSO | Configure identity provider and single sign-on settings |
Who can access these settings¶
Managing users and roles requires specific permissions:
organization:view— view organization informationuser:view,user:add,user:modify— manage usersrole:view,role:add,role:modify,role:delete— manage rolesidp-sso-authentication:view— configure SSO
If a tab or action is missing, ask a Tenant Admin to check your role.
Built-in roles¶
| Role | Who it's for |
|---|---|
Tenant Admin |
Full platform access — for platform administrators |
Tenant User |
Standard read access — for most team members |
Perspective Admin |
Full access within a Perspective scope |
Perspective User |
Read-only access limited to a Dynamic Perspective scope |
Asset Admin |
Resource inventory management access |
Executive User |
Dashboard and summary views — for leadership |
Partner Customer Admin |
For managed service provider customer accounts |
Partner Tenant Admin |
For managed service provider platform management |
See Roles and permissions for the full permission matrix.
Quick links¶
- Understand key concepts — roles, permissions, access scopes explained
- Create a custom role
- Invite and assign a user
- Set an access scope
- Set up Teams and Workspaces
- Validate access
- Troubleshoot access issues
Best practices¶
- Apply the principle of least privilege — give users only the permissions they need.
- Keep at least two tested administrators to avoid being locked out.
- Use Teams for shared access rather than repeating direct grants.
- Review stale users, external users, and inactive workspaces regularly.
- Test SSO configuration before broad enforcement.