Invite teammates to your organization, give each a role, and limit them to some projects. Billing stays with the owner.
Every account is an organization. Its owner can invite teammates by e-mail; members work on the organization's projects with the role they were given. Projects keep belonging to the owner's account: they use the owner's plan, limits and billing, and their URLs, API keys and data never change when people join or leave.
| Limit | Free | Pro | Scale | Enterprise |
|---|---|---|---|---|
| Team members (besides the owner) | 2 | 10 | 100 | 10,000 |
Pending invitations count towards the limit until they are accepted, revoked or expire.
#Roles
| Role | What it can do |
|---|---|
| Owner | Everything: billing, plan, prepaid credit and spending cap, members (including administrators), transferring the organization. |
| Administrator | Everything except billing: creates and deletes projects, restarts services, changes authentication settings, restores backups, sets automatic read replicas, invites and removes developers and read-only members, sees the activity log. |
| Developer | Builds in every project: Table Editor, SQL Editor (read and write), database objects, extensions, cron jobs, queues, Vault, storage, auth users, policies, the legacy Studio, API keys and the database password. Cannot create or delete projects, change authentication settings, restore backups or manage members. |
| Read-only | Views every project and runs read-only SQL (one SELECT, WITH, EXPLAIN, SHOW, VALUES or TABLE statement in a READ ONLY transaction). The service_role key, JWT secret, database password and connection strings are hidden; nothing can be changed. |
#Invite a member
- Open Team in the dashboard sidebar (it is called Organization when you work in an organization you joined), or Organization and team in the account menu.
- Choose Invite member, enter the e-mail address, pick a role and, optionally, the projects the member may use.
- The teammate receives an e-mail with an Accept invitation button. The link works once and expires after 7 days; Resend sends a new link and the old one stops working.
Teammates without an account create one with the invited address and then open the link again. Teammates who already have an account also see the invitation in their dashboard. An invitation can only be accepted by the account with the invited e-mail address.
If the invitation e-mail can't be sent, you get the link instead (Share the invitation link): send it to your teammate yourself. It works once and expires in 7 days.
Administrators can invite developers and read-only members; only the owner can invite or appoint administrators.
#Organization name
Owners and administrators rename the organization under General › Organization name on the Team page.
#API tokens and webhooks
Owners and administrators also have the API tokens and Webhooks tabs on the Team page: tokens for the whole organization and event webhooks, used to run StitchDB as the backend of your customers' apps. See Organization and project tokens and Webhooks.
#Several organizations
Your own organization is always there. Organizations you join appear in the switcher at the top of the dashboard sidebar; the dashboard shows the projects, plan and usage of the selected one, and new projects are created in it (owners and administrators only), counted against its owner's plan. Members of an organization never see its billing: the Billing page always belongs to your own account.
#Limit a member to some projects
When inviting, or later with Projects… next to a member, choose Only these projects. Other projects of the organization then answer 404 for that member. Choosing All projects includes projects created later.
#Change roles, remove and leave
- Change a member's role from the list; it applies to their next request.
- Remove takes access away immediately, also for the member's access tokens and AI tool connections.
- Members can Leave an organization from its settings page.
#Transfer ownership
The owner can transfer the organization to a member. Every project moves to the new owner's account, so the new owner's plan, limits and billing apply from then on; data, URLs and API keys do not change. The previous owner stays as an administrator, other members keep their roles, and both get an e-mail. The new owner's plan must allow the extra projects, and automatic read replicas that are running must be turned off first.
#Access tokens and AI tools
Access tokens and AI tool connections act as the member who created them: they reach the organizations the member belongs to, capped by the member's role. A read-write token of a read-only member works read-only, and a token stops working for an organization as soon as the member is removed.
#Activity
Owners and administrators see who did what under Team → View activity: invitations, joins and removals, project creation, deletion and restarts, and every change made in Studio (the SQL text itself is not recorded). Entries are kept for 180 days.