Access Control

Supabase provides granular access controls to manage permissions across your organizations and projects.

For each organization and project, a member can have one of the following roles:

• Owner: full access to everything in organization and project resources.
• Administrator: full access to everything in organization and project resources except updating organization settings, transferring projects outside of the organization, and adding new owners.
• Developer: read-only access to organization resources and content access to project resources but cannot change any project settings.
• Read-Only: read-only access to organization and project resources.
• No-access: no access to any organization or project resources by default. Use this for members who should only see the specific projects they're granted a project-scoped role on.

When you first create an account, a default organization is created for you and you'll be assigned as the Owner. Any organizations you create will assign you as Owner as well.

Manage organization members

To invite others to collaborate, visit your organization's team settings to send an invite link to another user's email. The invite is valid for 24 hours. For project scoped roles, you may only assign a role to a single project for the user when sending the invite. You can assign roles to multiple projects after the user accepts the invite.

Viewing organization members using the Management API

You can also view organization members using the Management API:

# Get your access token from https://supabase.com/dashboard/account/tokens
export SUPABASE_ACCESS_TOKEN="your-access-token"
export ORG_ID="your-organization-id"

# List organization members
curl "https://api.supabase.com/v1/organizations/$ORG_ID/members" \
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN"

Transferring ownership of an organization

Each Supabase organization must have at least one owner. If your organization has other owners then you can relinquish ownership and leave the organization by clicking Leave team in your organization's team settings.

Otherwise, you'll need to invite a user as Owner, and they need to accept the invitation, or promote an existing organization member to Owner before you can leave the organization.

Organization scoped roles vs project scoped roles

Each member in the organization can be assigned a role that is scoped either to the entire organization or to specific projects.

• If a member has an organization-level role, they will have the corresponding permissions across all current and future projects within that organization.
• If a member is assigned a project-scoped role, they will only have access to the specific projects they've been assigned to. They will not be able to view, access, or even see other projects within the organization on the Supabase Dashboard.

This allows for more granular control, ensuring that users only have visibility and access to the projects relevant to their role.

To default a member to zero project access and grant access on a per-project basis, assign them the organization-level No access role, then grant project-scoped roles for the specific projects they need. The No-access role is omitted from the permission tables below since it has none of the listed permissions by default.

Organization permissions across roles

The table below shows the actions each role can take on the resources belonging to the organization.

Project permissions across roles

The table below shows the actions each role can take on the resources belonging to the project.