Skip to main content

Capabilities

The Supabase connector syncs the following resources:
  • Organization Members: Platform-level users synced per organization with roles (Owner, Administrator, Developer, Read-only).
  • Auth Users: Project-level users synced per project with database roles managed via Auth Admin API.
  • Organizations: Supabase organizations with role-based entitlements.
  • Projects: Supabase projects with per-project database role entitlements and provisioning (grant assigns role, revoke authenticated removes user).

Gather Supabase credentials

To configure the Supabase connector, you need a Personal Access Token (PAT) for the Supabase Management API. The connector automatically discovers all active projects and fetches each project’s service_role key at provisioning time — no separate project credentials are required for sync.
1
Log in to Supabase at https://supabase.com/dashboard.
2
Navigate to Account Settings > Access Tokens: https://supabase.com/dashboard/account/tokens.
3
Click Generate new token, name it (e.g., conductorone-connector), and click Generate token.
4
Copy the token immediately — it starts with sbp_ and is shown only once.

Configure the Supabase connector

Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Supabase and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Enter the required configuration:
  • Supabase Access Token: The Personal Access Token (PAT) you generated.
9
Click Save.
10
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Supabase connector is now pulling access data into C1.

Provision access

The Supabase connector supports provisioning for Projects — you can grant and revoke database roles for auth users and organization members.
Provisioning requires the --provisioning flag (-p) when running the connector manually, or Accounts Management enabled in C1. The connector automatically fetches each project’s service_role key from the Management API using the same PAT — no separate project credentials are needed.

Find a project ID

Project IDs (also called reference IDs) are required to target provisioning commands.
1
In the Supabase dashboard, select the target project.
2
Go to Project Settings > General.
3
Copy the Reference ID (labeled “Reference used in APIs and URLs”, e.g., zqzeuactwzbejpvhrkqy).
You can also find resource IDs (UUIDs) for auth users and organization members by running baton resources --file sync.c1z after a sync.

Grant a database role

Grant a database role to an auth user:
Grant a database role to an organization member (cross-type grant — creates the user in the project if they don’t exist):

Revoke a database role

Revoke a custom role (resets the user’s role to authenticated, the default PostgreSQL role):
Revoke the authenticated role (removes the user from the project entirely):
Revoking the authenticated role permanently deletes the user from the project via the Supabase Auth Admin API. This action cannot be undone through the connector.

The connector automatically syncs auth users from all active Supabase projects accessible via the PAT. Each auth user is linked to its parent project, so users from different projects are properly distinguished. Auth users and organization members appear as separate resource types in C1 — both are visible in the Accounts tab of the application.