Skip to main content

​
What this check does

DSALTA lists the Supabase organization’s members (Management API) and checks them against the allowed users.
This check also runs on 85 other integrations — see User access to Critical System should be valid for the full list.
Passes when: Only authorized members retain active access to the Supabase organization.
Check parameters. This check evaluates against the following defaults:
  • allowedEmails: []

​
Why this matters

Access to a backend platform holding production data must be restricted to authorized people.

​
How to fix

Review Supabase organization access
  1. Sign in to the Supabase dashboard and select your organization.
  2. Go to Organization Settings → Team to list every member and their Role (Owner, Administrator, Developer).
  3. In DSALTA, open Data Library → Access (or this test’s Source Data tab) to see which Supabase members have no matching active employee.
  4. For each of those, click the ⋯ at the end of the member row and choose Remove member.
  5. For members who still belong but hold more access than they need, use Manage role to set the least-privileged role for their job.
  6. Revoke any entries still listed as Invited that are no longer needed.
  7. In DSALTA → People, confirm each remaining Supabase member exists and is Active.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.