Administration¶
This section covers everything needed to manage CloudVerse AI for your organization — user accounts, role-based access control, business scope configuration, notifications, and organization settings.
What's in this section¶
| Area | Use it to |
|---|---|
| Users & Roles | Invite users, assign roles, and manage access permissions |
| Key concepts | Understand users, roles, permissions, and access scopes |
| Roles and permissions | Review built-in roles and their permission sets |
| Create a role | Build a custom role with specific permissions |
| Assign users | Add users and assign roles |
| Access scopes | Limit what users see using Perspective-based scopes |
| Teams & Workspaces | Group users and organize resources into access boundaries |
| Perspectives | Map cloud resources to business teams, products, and environments |
| Organization Settings | Configure currency, branding, and org-level preferences |
| Notifications | Set up alert delivery for anomalies, budgets, and recommendations |
| Profile & Preferences | Manage your personal settings and display preferences |
Who administers CloudVerse AI¶
The Tenant Admin role has full access to all administration pages. Other roles may have limited access depending on their permission set. If you are missing a tab or action, ask a Tenant Admin to review your role.
Common admin workflows¶
Invite a new user → Assign users → choose role → optionally set a Dynamic Perspective scope.
Create a scoped user for a team lead → Create a role with view-only permissions → Assign users → set Access scope to their team's Perspective.
Map costs to business teams → Perspectives → create a Perspective per team → attach cost allocation rules.
Set up SSO → Organization Settings → SSO tab → configure your identity provider.
Route anomaly alerts to Slack → Notifications → select Slack as the channel → choose which alert types to route.
Access model overview¶
CloudVerse AI uses roles, permissions, teams, workspaces, and access scopes to control what users can see and change.
Users with a Dynamic Perspective scope see only cost data matching that scope. Use the smallest role and scope that lets each user do their job.