Supabase

Connect Supabase to collect infrastructure evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Supabase:

   1. In the Supabase dashboard, open your account's Access Tokens page (dashboard/account/tokens).
   2. Generate a new token and make it a scoped token: choose the organization and projects Safeguard should read.
   3. Grant only Read permissions, for example Database: Read and Project Settings: Read, not Read-write.
   4. Copy the token (it starts with sbp_) right after it is created.

   Supabase's public documentation does not cover every step.

   Source: supabase.com, supabase.com, checked 2026-10-07.

   The permissions Safeguard needs: organizations:read, projects:read, database:read.

2. On Compliance › Connectors, open Supabase, click Connect, choose API token and fill in:

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Connect with the MCP server

Choose MCP server: the address https://mcp.supabase.com/mcp is filled in. Sign in to Supabase when asked. It lets Griffin AI search Supabase; the compliance evidence comes from the API token connection.

Frameworks

Safeguard's automated tests read Supabase and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Infrastructure connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks