Access model
How organization roles, team roles and workspace access combine into what a person can see and change in Costfluent.
What a person can do in Costfluent comes from three things: their organization role, the teams they belong to with a team role in each, and the access each of those teams has to a workspace. Costfluent checks every action on the server against that combination. A person who belongs to several organizations has a separate role in each.
Organization roles
Every member of an organization has one organization role. It decides what they can do across the organization.
An Owner can do everything: organization settings, billing and plans, single sign-on, users and teams, which teams can access each workspace, creating, renaming and deleting workspaces, connections, tag keys, API tokens, notification channels, the audit log, and Export your data. An Owner can do everything in every workspace without being on a team. An Integration owner can do what an Editor can, and also connect and manage cloud accounts and manage tag keys. An Editor creates API tokens, syncs connections and sets up notification channels. A Viewer sees the organization, its plan, its members and its connections. Every role sees the organization's subscription, except in an organization a partner manages, where only the partner's managers see it.
The table lists every organization capability by the label the API token dialog uses, and which role holds it.
| Capability | Owner | Integration owner | Editor | Viewer |
|---|---|---|---|---|
| Organization and workspaces | ||||
| View organization | ✓ | ✓ | ✓ | ✓ |
| View subscription | ✓ | ✓ | ✓ | ✓ |
| Create workspaces | ✓ | – | – | – |
| Update workspaces | ✓ | – | – | – |
| Delete workspaces | ✓ | – | – | – |
| Integrations | ||||
| View integrations | ✓ | ✓ | ✓ | ✓ |
| Manage integrations | ✓ | ✓ | – | – |
| Sync integrations | ✓ | ✓ | ✓ | – |
| Costs and anomalies | ||||
| Manage bucket export | ✓ | ✓ | – | – |
| Allocation and tags | ||||
| Manage tag keys | ✓ | ✓ | – | – |
| Users, teams and channels | ||||
| Update organization | ✓ | – | – | – |
| Delete organization | ✓ | – | – | – |
| Export organization | ✓ | – | – | – |
| Manage billing | ✓ | – | – | – |
| Manage single sign-on | ✓ | – | – | – |
| Provision identities | ✓ | – | – | – |
| Manage workspace access | ✓ | – | – | – |
| Invite users | ✓ | – | – | – |
| Manage users | ✓ | – | – | – |
| Remove users | ✓ | – | – | – |
| View members | ✓ | ✓ | ✓ | ✓ |
| Create teams | ✓ | – | – | – |
| Manage teams | ✓ | – | – | – |
| Delete teams | ✓ | – | – | – |
| Create API tokens | ✓ | ✓ | ✓ | – |
| Revoke API tokens | ✓ | – | – | – |
| View API tokens | ✓ | ✓ | ✓ | – |
| Manage connected apps | ✓ | – | – | – |
| Create notification channels | ✓ | ✓ | ✓ | – |
| Update notification channels | ✓ | ✓ | ✓ | – |
| Delete notification channels | ✓ | ✓ | ✓ | – |
| Test notification channels | ✓ | ✓ | ✓ | – |
| View audit log | ✓ | – | – | – |
| Require two-factor authentication | ✓ | – | – | – |
| Manage managed organizations | ✓ | – | – | – |
| Support requests | ||||
| Use support | ✓ | ✓ | ✓ | ✓ |
| View all support requests | ✓ | – | – | – |
| Kubernetes | ||||
| Report Kubernetes usage | ✓ | – | – | – |
Change a person's role under Settings, then Users; see Users, teams and roles. An Owner can be lowered to another role while at least one other active Owner remains.
Export your data under Settings, then Organization, downloads the organization's configuration as JSON with Download configuration: members, teams, connections, workspaces, reports, dashboards, budgets, alerts and allocation. It holds no cost data; cost is exported per workspace as CSV.
Notification channels belong to the organization, so who can set them up follows the organization role alone; a team role adds nothing there.
Team roles and workspace access
Inside a workspace, anyone other than an organization Owner acts through a team. A team has members, each with a team role, and it is granted access to workspaces, each at one level. Only an organization Owner grants or changes a team's access, and only an Owner creates, renames or deletes a workspace.
A team Editor creates and changes the workspace's work: cost reports, saved filters, dashboards, folders, budgets, alerts, segments, allocation rules and virtual tags, share links and report schedules; they switch the workspace's data sources on or off and remove them, while linking one or choosing its accounts also needs the Owner or Integration owner organization role; they acknowledge, archive and ignore anomalies and manage savings items. A team Viewer reads cost, reports and their schedules, dashboards, budgets, anomalies, segments, allocation, tags and savings items. The last column marks what a team's Can view access withholds.
| Capability | Editor | Viewer | Withheld under “Can view” |
|---|---|---|---|
| Organization and workspaces | |||
| View workspaces | ✓ | ✓ | – |
| Integrations | |||
| Add integrations to workspaces | ✓ | – | ✓ |
| Remove integrations from workspaces | ✓ | – | ✓ |
| Costs and anomalies | |||
| View costs | ✓ | ✓ | – |
| Export costs | ✓ | ✓ | – |
| Submit cost estimates | ✓ | – | ✓ |
| View anomalies | ✓ | ✓ | – |
| Acknowledge anomalies | ✓ | – | ✓ |
| Reconcile invoices | ✓ | – | ✓ |
| Budgets and cost alerts | |||
| View budgets | ✓ | ✓ | – |
| Create budgets | ✓ | – | ✓ |
| Update budgets | ✓ | – | ✓ |
| Delete budgets | ✓ | – | ✓ |
| Manage cost alerts | ✓ | – | ✓ |
| Reports and dashboards | |||
| View cost reports | ✓ | ✓ | – |
| Create cost reports | ✓ | – | ✓ |
| Update cost reports | ✓ | – | ✓ |
| Delete cost reports | ✓ | – | ✓ |
| View dashboards | ✓ | ✓ | – |
| Create dashboards | ✓ | – | ✓ |
| Update dashboards | ✓ | – | ✓ |
| Delete dashboards | ✓ | – | ✓ |
| Create saved filters | ✓ | – | ✓ |
| Update saved filters | ✓ | – | ✓ |
| Delete saved filters | ✓ | – | ✓ |
| Create folders | ✓ | – | ✓ |
| Update folders | ✓ | – | ✓ |
| Delete folders | ✓ | – | ✓ |
| View report schedules | ✓ | ✓ | – |
| Manage report schedules | ✓ | – | ✓ |
| Manage share links | ✓ | – | ✓ |
| Manage business metrics | ✓ | – | ✓ |
| Allocation and tags | |||
| View tags | ✓ | ✓ | – |
| Manage tags | ✓ | – | ✓ |
| View cost allocation | ✓ | ✓ | – |
| Manage cost allocation | ✓ | – | ✓ |
| Savings | |||
| View savings | ✓ | ✓ | – |
| Manage savings | ✓ | – | ✓ |
| Respond to savings | ✓ | – | ✓ |
Every team role can export cost to CSV.
The organization role is the ceiling of every team role: a team never gives a person more than their organization role allows. A Viewer acts as a team Viewer on every team, whatever role the team gives them, and lowering someone's organization role lowers what they can do on every team at once.
| Workspace access | Effect |
|---|---|
| Can edit | The team's roles apply in full. |
| Can view | The team's roles lose their editing rights in this workspace, share links and report schedules included. |
| No access | The team grants nothing in this workspace. |
A person on several teams gets everything any of those teams grants.
The Everyone team
Every organization has a system team, Everyone, and every member is on it with the team role that follows their organization role: Editor for an Owner, Integration owner or Editor, Viewer for a Viewer. A new workspace gives Everyone the organization's Default workspace access, and that grant stays when other teams are given access. Set the default under Settings, then Organization.
Restrict all workspaces under Settings, then Teams, closes the organization in one step: Everyone gets No access on every workspace, and workspaces created afterwards start with No access for it. Teams keep the access they grant. To see what a person reaches in each workspace and which team grants it, open their Workspace access under Settings, then Users.
API tokens
A Public API token carries its own capabilities and, optionally, one workspace. Listing the organization's tokens takes View API tokens, which a Viewer does not have, and a member sees only the workspace tokens of workspaces they can view. When it is created, it cannot be given more than the person creating it could do, and the dialog offers only that. An organization token reaches every workspace, so only an Owner gives one workspace capabilities; a workspace token carries workspace capabilities only. When a token other than a service token is used, its workspace capabilities reach only where its creator still holds them, a workspace token's within its one workspace, and each organization capability works only while its creator still holds it, so lowering someone's role lowers what their tokens can do; only Report Kubernetes usage stays as created. A token is never revoked on its own, but an organization or workspace token stops working while its creator is not an active member and works again if they return; the Kubernetes agent's cluster token keeps working. The list shows a creator who left, and says Creator no longer has this access on a workspace token whose creator, still a member, no longer holds all of its capabilities in its workspace, or an organization token whose creator, still a member, no longer holds one of its organization capabilities; meanwhile the token is refused what its creator no longer holds. The Owner or the token's creator revokes it. See API authentication.