> ## 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.

# Supabase

> How DSALTA integrates with Supabase — data collected, setup guide, and automated compliance checks.

## Overview

DSALTA connects to Supabase using read-only API access to collect compliance evidence automatically. Data syncs every 24 hours and feeds into your Data Library modules.

<Info>
  **Read-only access.** DSALTA never modifies, creates, or deletes resources in your Supabase account.
</Info>

## How to Connect

Supabase connects with a read-only **Management API token** (`sbp_…`).

<Steps>
  <Step title="Create a Management API token">
    In Supabase, open your **account menu → Access Tokens** ([supabase.com/dashboard/account/tokens](https://supabase.com/dashboard/account/tokens)) and **Generate new token**. Copy the `sbp_…` value.
  </Step>

  <Step title="Connect">
    In the DSALTA sidebar, go to **Integrations**, find **Supabase**, and click **Connect**. Paste the token in the secure window and submit.
  </Step>

  <Step title="Finish">
    DSALTA runs an initial sync — usually a few minutes — after which the compliance checks below activate.
  </Step>
</Steps>

## Automated Compliance Checks

Each check below runs automatically every 24 hours. Click any check for step-by-step remediation guidance.

| Check                                                                                                                   | Description                                                               |
| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [User access to Critical System should be valid](/integrations/supabase/user-access-to-critical-system-should-be-valid) | Checks that users with access to the Supabase project are authorized.     |
| [Offboarded users should not have active access](/integrations/supabase/offboarded-users-should-not-have-active-access) | Checks that offboarded employees no longer retain active Supabase access. |

## Troubleshooting

<AccordionGroup>
  <Accordion title="Integration shows Disconnected">
    Re-authenticate from **Integrations → Supabase → Reconnect**. This can happen if the Management API token was revoked.
  </Accordion>

  <Accordion title="Data is not syncing">
    Confirm the Management API token is still valid and can view organization members, then trigger a manual sync from the integration settings.
  </Accordion>
</AccordionGroup>