Members
Invite people to the team, manage seats, and remove access cleanly.
Members belong to a team. Within it, access to individual projects and datasets is granted separately — being a member is the entry ticket, not a key to everything.
Invite someone
Open Settings → Members
Click Invite member.
Enter email addresses
Multiple addresses at once, comma-separated. Each gets its own invitation.
Choose a team role
The role sets what they can do team-wide. Project-level access is granted separately — see Roles and permissions.
Optionally pre-assign projects
Saves the new member from having to request access to the projects they obviously need.
Invitations expire after 14 days. Pending invites appear at the top of the members list and can be resent or revoked.
Invites consume a seat on acceptance, not on sending
You can invite more people than you have seats; the seat is taken when they accept. If seats run out, later acceptances are blocked until you free one.
The members list
| Column | Meaning |
|---|---|
| Member | Name, email, and avatar initials |
| Role | Team role |
| Projects | How many projects they can open |
| Last active | Most recent session |
| Status | Active, Invited, or Suspended |
Change someone’s role
Use the ⋮ menu on their row. Role changes take effect immediately — no re-login required.
Downgrading does not revoke project roles
Dropping someone from Admin to Member leaves their existing project roles intact. If you are removing responsibilities, check their projects too.
Suspend or remove
| Action | Effect | Reversible |
|---|---|---|
| Suspend | Sessions end, seat still consumed, content untouched | Yes |
| Remove | Sessions end, seat freed, project roles revoked | Content stays |
You cannot remove the last admin
Every team must keep at least one admin — the person who controls roles and payments. Removing, suspending, or demoting the only one is refused. Promote a replacement first.
Removing a member never deletes their work. Charts, dashboards, and datasets they created stay in their projects and are reassigned to a team admin.
Check what they connected first
A source connected with credentials tied to one person — a database login in their name, an API key they created — breaks when that account is disabled upstream. Move those sources onto a service account before removing the member. The Sources list shows who created each one.
Seats and plans
| Plan | Seats | Guests |
|---|---|---|
| Free | 3 | — |
| Pro | 25 included, more available | Unlimited viewers on shared links |
| Enterprise | Negotiated | SSO / SCIM provisioning |
Guests who only open a shared link do not consume a seat. See Sharing.
SSO and provisioning
Enterprise teams can enforce SAML SSO and sync membership from your identity provider with SCIM. When SCIM is on, the members list becomes read-only — deprovisioning in your IdP removes the member here automatically.