Logo
Search
API Docs

Team Invitations & Roles

Account & Team Management

Team Invitations & Roles

Overview

Adding people to your organization is done by inviting them from the org's users page in the dashboard. This page covers the invite workflow itself — the email/role/invite steps, the three available roles, and why there's no SCIM provisioning. For the full breakdown of RBAC permissions and SSO configuration, see Team Management & SSO.


Inviting Users

You can invite up to 100 users at once from your organization's users page in the dashboard:

  1. Enter an email address
  2. Select a role for that invite — Editor or Admin
  3. Repeat for each additional person you want to invite
  4. Click Invite

Each invited email gets its own role assignment, so you can mix Editors and Admins in a single batch invite.


Choosing a Role

Three roles exist overall:

RoleAccess
AdminRead and write everything
EditorRead and write everything except Org Settings, Billing, Members, and API Keys
ViewerRead-only access to everything except Org Settings, Billing, Members, and API Keys

The invite screen itself only offers a choice between Editor and Admin — Viewer access is assigned afterward, by changing a member's role once they've joined. Editor is the recommended role for developers, since it gives full build and test access without exposing billing or member management.


No SCIM Provisioning

The core system does not support SCIM provisioning. Each user must create their own account first — an organization admin cannot pre-provision an account on someone's behalf. Once that person has an account, an admin invites them into the organization and assigns their role. Keep this in mind if you're used to identity-provider-driven user provisioning elsewhere: account creation and org invitation are always two separate steps here.