Admin
Tenancy management — who has access, how the workspace estate is structured, which clouds and tools are connected, and how identity is federated.
The Admin group manages the tenancy itself: who has access, how the workspace estate is structured, which clouds and tools are connected, and how identity is federated.
In a typical deployment these are configured once during onboarding and revisited only as the organisation changes.
The seven modules
Access and structure
Organization
User and access administration — creating team members, assigning page and action permissions, reviewing activity.
Workspace Setup
Workspace lifecycle — creating, renaming, deleting, and seeding demo workspaces for evaluation and training.
Identity & SSO
Enterprise identity federation — OIDC and SAML single sign-on, and SCIM 2.0 automated provisioning.
Org Analytics
Organisation-level analytics spanning every workspace — aggregate spend, coverage, and control adoption.
Connections
Cloud Accounts
Registering and verifying credentialed links to AWS, Azure, GCP, and OCI. The prerequisite for every data-bearing module.
Integrations
The external connection hub — issue tracking, chat alerting and approvals, source control, Kubernetes ingestion, execution windows.
AI Provider Accounts
Direct connections to LLM providers, so AI spend outside the cloud bill is consolidated with the rest.
The two that block everything else
Cloud Accounts is the prerequisite for every data-bearing module. Nothing else works properly until connections are verified.
Integrations is what makes the product reach people — alerts, approvals, and findings routed into Slack, Teams, Jira, and Linear. A cost platform that requires people to visit it fails, because they do not.