> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# User access to Critical System should be valid

> Checks that users with access to the Supabase project are authorized.

Checks that users with access to the Supabase project are authorized.

## About

When you connect Supabase to DSALTA, the platform syncs your Supabase members and their access using read-only API access. DSALTA evaluates this control on every sync. DSALTA lists your Supabase organization members (Management API) and checks them against the allowed users.

## Why This Matters

Access tends to accumulate over time as roles change, leaving people with more than they need. Excess access widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach critical systems is a core control in SOC 2 and ISO 27001.

## How to Fix

**Before you begin**

* Ensure the Supabase integration is connected so DSALTA has the current list of members.

**Validate access**

1. In the **Supabase** dashboard, open **Organization settings → Team**, review members, and remove anyone who is not a current, authorized employee.
2. In DSALTA, go to **Data Library → Access**, filter for **Supabase**, and mark each reviewed member as **In Scope** (valid) or **Not in Scope** (to be revoked), recording the reviewer.
3. Set a recurring access review schedule (quarterly is recommended).

Once all members have valid, documented access, DSALTA sets the check status to **Passing**.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    This check runs automatically every 24 hours while the Supabase integration is connected. You can also trigger a manual sync from **Integrations** in the sidebar.
  </Accordion>

  <Accordion title="What happens if it keeps failing?">
    A failing check appears in your **Data Library → Tests** dashboard. Work through the steps above; once access is corrected, the status updates automatically on the next sync.
  </Accordion>

  <Accordion title="Can I exclude this check?">
    Yes. If it does not apply to your environment, mark it as **Not Applicable** with a justification. The exclusion is documented for auditors.
  </Accordion>

  <Accordion title="Does DSALTA change my Supabase configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Supabase.
  </Accordion>
</AccordionGroup>