Set up a Supabase connector

Capabilities

The Supabase connector syncs the following resources:

Resource	Sync	Provision
Organization Members
Auth Users
Organizations
Projects

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.

Navigate to Account Settings > Access Tokens: https://supabase.com/dashboard/account/tokens.

Click Generate new token, name it (e.g., conductorone-connector), and click Generate token.

Copy the token immediately — it starts with sbp_ and is shown only once.

Configure the Supabase connector

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Apps > Connectors and click Add connector.

Search for Supabase and click Add.

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.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

Enter the required configuration:

Supabase Access Token: The Personal Access Token (PAT) you generated.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Supabase connector is now pulling access data into C1.

Follow these instructions to use the Supabase connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals.

Step 1: Set up a new Supabase connector

In C1, navigate to Apps > Connectors and click Add connector.

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

In the Settings area of the page, click Edit, then click Rotate to generate a new Client ID and Secret. Carefully copy and save these credentials.

Step 2: Create Kubernetes configuration files

Secrets configuration

# baton-supabase-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-supabase-secrets
type: Opaque
stringData:
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  BATON_SUPABASE_ACCESS_TOKEN: <Supabase Personal Access Token>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

Deployment configuration

# baton-supabase.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-supabase
  labels:
    app: baton-supabase
spec:
  selector:
    matchLabels:
      app: baton-supabase
  template:
    metadata:
      labels:
        app: baton-supabase
        baton: "true"
        baton-app: supabase
    spec:
      containers:
      - name: baton-supabase
        image: public.ecr.aws/conductorone/baton-supabase:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-supabase
        envFrom:
        - secretRef:
            name: baton-supabase-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Applications. On the Managed apps tab, locate and click the name of the application you added the Supabase connector to. Supabase data should be found on the Entitlements and Accounts tabs.

Done. Your Supabase connector is now pulling access data into C1.

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.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Supabase connector

Capabilities

Gather Supabase credentials

Configure the Supabase connector

Step 1: Set up a new Supabase connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather Supabase credentials

​Configure the Supabase connector

​Step 1: Set up a new Supabase connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Supabase credentials

Configure the Supabase connector

Step 1: Set up a new Supabase connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector