Giving your team access

Invite people, choose Owner, Admin or Member roles, remove users and limit what they see.

Giving your team access

Invite colleagues to your CostGlass organisation, choose what each person is allowed to do, and (if you want) limit what they can see.

Where in CostGlassSettings → Team
PlanAll plans
Who can do thisOwner and Admin (Members can view the list)
Time needed5 minutes
In short
  • Everyone in your organisation has one of three roles: Owner, Admin or Member.
  • Owners and Admins invite people and change roles. Only Owners can create, demote or remove other Owners.
  • An organisation always keeps at least one Owner. CostGlass will not let you remove or demote the last one.
  • Invitations only work for the email address you typed. People sign in with Google, with a password, or (if you set it up) through your company single sign-on.
  • You can limit a person to one part of your organisation (a node in the hierarchy) so they only see that part's spend.
Before you begin
  • You are signed in as an Owner or an Admin of your organisation.
  • You know the work email address of the person you want to invite.
  • The person does not already belong to another CostGlass organisation (an email address can belong to only one).

The three roles

A role is a label on each person that decides which actions they may take. Every person in your organisation has exactly one.

RoleWho it suitsWhat it can do
MemberEngineers, team leads and finance analysts who need to look at cost data.Sees the dashboards, Cost Explorer, reports and other pages for the part of the organisation they are allowed to see. Cannot change organisation-wide settings.
AdminFinOps practitioners and platform leads who run the day-to-day setup.Everything a Member can do, plus: invite Members and Admins, change roles between Member and Admin, remove Members and Admins, and manage the settings listed below.
OwnerThe person accountable for the account, for example a CTO or Head of Infrastructure.Everything an Admin can do, plus: create other Owners, change or remove Owners, and cancel the subscription.

Actions that need Owner or Admin

CostGlass checks the role on its servers, not only on screen, for these actions:

  • Inviting people, changing roles and removing people (this page).
  • Setting up single sign-on, creating API keys and reading the audit log.
  • Connecting Jira, creating cost alerts, and changing anomaly alert rules and anomaly settings.
  • Creating, editing and deleting virtual tags and their rules, and changing tag policies.
  • Creating or changing unit economics metrics.
  • Changing uptime alert settings and starting a paid subscription (billing).

Actions that need Owner

  • Promoting someone to Owner.
  • Changing the role of, or removing, another Owner.
  • Cancelling the subscription.
Note
The permissions table on the Team page (Role-Based Access Control (RBAC) Permissions Matrix) is a summary. If it differs from this page, this page describes what the servers enforce. For example, an Admin can invite another Admin, although the table says "Members only".

Invite a teammate

1
Open the Team page
In the left menu choose Settings, then Team (under Organisation). The page lists everyone in your organisation.
Settings → Team: the summary cards, the member table and the Invite Teammate button.
2
Start the invitation
Click Invite Teammate. A dialog called Invite a Teammate opens.
3
Enter their details
Type their work email in Work Email Address. Optionally add their name in Full Name.
4
Choose a role
Pick Member (the default) or Administrator. Owners also see an Owner card, but see the note below before using it.
5
Send it
Click Send Invitation. The person is added to the list with the status Invited, and an email is sent to them.
Inviting an Owner
The server only accepts Member or Admin in an invitation. To make someone an Owner, invite them as an Admin first, then an Owner changes their role to Owner in the member table (see Change a role).

What the invited person does

  1. They open the invitation email. If CostGlass sent a temporary password, they sign in with it and choose a new one.
  2. Or they click Continue with Google on the sign-in page, using the same email address you invited.
  3. If your organisation uses single sign-on, they type their work email on the sign-in page and choose Continue with SSO.
  4. On first sign-in their status changes from Invited to Active.

An email address that CostGlass does not know is never let in just because it can sign in with Google. If someone signs in with an address that was not invited, they see a message asking them to ask an administrator for an invitation.

If the invitation is refused

  • "That email already belongs to another organisation": each email address can belong to one organisation. The person needs to use a different address, or be removed from the other organisation first. CostGlass also gives this message when the address is registered in another region, and it does not say where.
  • The person was removed earlier: inviting them again re-activates their record as a fresh invitation with the role you choose.

How to read the member table

ColumnWhat it shows
MemberName and email. A small "you" marker shows your own row. Use the copy button to copy an email.
Role & PermissionsThe person's role. For Owners and Admins managing the team this is a drop-down so you can change it.
StatusActive (has signed in), Invited (waiting for first sign-in), or Disabled. Removed people no longer appear in the list.
Auth MethodGoogle SSO (signed in with Google), Email (email and password), Enterprise SSO (your SAML provider) or OIDC.
Last Sign-inWhen they last signed in.
ActionsA Remove button. Your own row says Current user and a sole Owner shows Sole owner, because neither can be removed.

The four cards at the top count Total Teammates, Active Accounts, Pending Invitations and Privileged Access (Owners plus Admins). Use the search box to find people by name or email, and the filters to narrow by role or status.

Change a role

1
Find the person
In the member table, find their row.
2
Pick the new role
Use the drop-down in Role & Permissions. The change is saved straight away and a message confirms it.
  • Admins can switch people between Member and Admin. They cannot touch an Owner and cannot create one.
  • Owners can change anyone, and the Owner option appears in the drop-down only for them.
  • Last-owner rule: if there is only one Owner, that Owner cannot be demoted. Make a second person an Owner first.

Remove someone

1
Click Remove
In the person's row click Remove. A dialog called Remove team member? opens.
2
Confirm
Click Remove Teammate. They lose access straight away.
  • You cannot remove yourself.
  • Only an Owner can remove an Owner, and never the last one.
  • Removing a person does not delete what they created (saved views, reports and so on stay in the organisation). Their sign-in is disabled.
  • Removals are written to the audit log.

Limit what someone can see (scoped access)

By default a person sees the whole organisation. You can instead bind them to one node of your organisation hierarchy, for example "Payments team". They then see only the cloud accounts under that node and everything below it. This is done on the Hierarchy page, not on the Team page.

1
Build your hierarchy first
Create the nodes and place your cloud accounts in them. See Setting up your organisation hierarchy.
2
Bind the person
Open Settings → Hierarchy, select a node, and under Team Permissions & Scoped Access click + Scope Team Member.
3
Check it
The person's access changes within about 30 seconds. To undo it, remove the binding from the same panel and they see the whole organisation again.
Scope is not a role
A role says what a person may do. Scope says which accounts they may see. A scoped Member is still a Member, and a scoped Admin can still change settings. Some pages are not narrowed by scope (see which pages respect scope), so do not rely on scope as the only way to hide figures from someone.

If your organisation requires single sign-on

When an Owner or Admin switches on Require single sign-on (see Single sign-on), people whose email is on a verified company domain can no longer sign in with a password or Google. They must use your identity provider. One Owner, chosen as the break-glass account, keeps password sign-in so a problem at your provider cannot lock you out.

Single sign-on does not create accounts. Invite people here first, then they sign in through your provider.

Your own profile

Every person can open Settings → Profile (#settings:profile) to change their own display name and phone number. The page also shows your role, your organisation and plan, how you sign in and when you last signed in. Your email address is not editable there.

Settings → Profile: your name, phone number, role and sign-in method.

A worked example

Adding a finance analyst and a second Owner

A company has one Owner, Sam. Sam wants Priya (finance) to look at spend but change nothing, and wants a second Owner for safety.

  1. Sam clicks Invite Teammate, enters Priya's email, leaves the role as Member, and clicks Send Invitation.
  2. Sam invites Jo (the CTO) as an Administrator. After Jo signs in, Sam changes Jo's role to Owner in the table.
  3. Now there are two Owners, so either could be demoted later without breaking the last-owner rule.

The names here are illustrative.

Frequently asked questions

I invited someone but they say they cannot sign in.
Check that they use exactly the email address you invited. If your organisation requires single sign-on, they must use it. If they never received the email, ask them to check spam, then try Continue with Google.
Can one person belong to two organisations?
No. An email address can belong to one organisation. A colleague who needs both should use a different address for the second.
Is there a limit on the number of users?
This page does not show a limit. Your plan limits the number of cloud connections, not people. See Billing & Plans for what your plan includes.
Can I see who changed a role or removed a person?
Yes. Open Settings → Audit Log. Invitations, role changes and removals are recorded with who did them.
What happens to someone's saved views and reports when I remove them?
They stay in the organisation. Only the person's access is removed.

Related guides