How DSALTA integrates with Supabase — data collected, setup guide, and automated compliance checks.
Overview
How to connect
Automated checks
Useful links
DSALTA connects to Supabase using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Supabase account.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.
DSALTA reads the member roster of every Supabase organization the token can see — names, emails, organization roles and MFA status, which appears on your Access page. Supabase’s members API reports no account status, so every member is listed as Active; and every project the token can see, which appears on your Inventory page with its region and status.It calls these Supabase endpoints:
/v1/organizations
/v1/organizations/{slug}/members
/v1/projects
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Supabase environment.
There is no Reconnect button. Open Integrations → Connected, click Manage on the Supabase card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Supabase. This can happen if the Management API token was revoked.
Data is not syncing
Confirm the Management API token is still valid and can view organization members, then click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once.
Connect with a Supabase Management API token to sync your team and projects. DSALTA only makes read (GET) calls.Before you begin
A Supabase account that can view organization members
You will need:
Field
Where to find it
Example
Management API token
Supabase → account menu → Access Tokens → Generate new token. · Open
sbp_…
1
Start in DSALTA
Open Integrations in the DSALTA sidebar, find Supabase, and click Connect to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
2
Integrating Supabase with DSALTA means
DSALTA will use your token to read your Supabase organization members (access reviews) and projects (inventory) for compliance monitoring.
3
Create a Management API token
Generate a Supabase Management API token from your account settings (account menu → Access Tokens → Generate new token). Supabase tokens cannot be scoped down — the token inherits your own permissions — so treat it like a password; DSALTA only sends read (GET) requests with it.
Supabase shows the token value once, immediately after Generate new token — copy it then, because the Access Tokens list only ever shows a masked version. By default the token has no expiry, and it is not restrictable: a Supabase personal access token carries the same privileges as the account that created it, so store it like a password and revoke it from the same screen when it is no longer needed. DSALTA only ever sends GET requests with it.
Create the token with an account whose Supabase membership is limited to the organization you want reviewed. DSALTA walks every organization the token can see and syncs the members of each, and it lists every project the token can see — so a personal side-project organization on the same login will appear on your Access and Inventory pages too.The Role column on the Access page is the Supabase organization role: Owner (full access), Administrator (full access except organization settings, transferring projects out and adding owners), Developer (read-only on the organization, content access on projects) or Read-Only (read-only everywhere; Team and Enterprise plans only). Use it when you review who should keep access.
4
Enter your token
Paste your Management API token below and click Connect.
DSALTA validates the credential when you click Connect. On success the integration moves to the Connected tab, and Manage → Status reads Connected and working properly. Checks begin reporting after the first sync.
If the connection is rejected. Invalid token. Generate a Management API token from Supabase → Access Tokens.The on-screen message is generic — see Connection error messages.
Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)
