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

# Statsig

> Feature flags & experimentation — users & access

<Tabs>
  <Tab title="Overview">
    Connect Statsig with a Console API key to sync project users, feature gates and experiments, and run access reviews. Read-only.

    <Info>
      **Read-only access.** DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
    </Info>

    <Info>
      **What you'll see.** The Access page lists the **users** of one Statsig project — the project the key belongs to — with their name, email and project role. Statsig reports no account status, join date or MFA state, so every user is shown as **Active** with MFA **Unknown**, and each row is stamped with the date of the sync.
    </Info>

    <Note>
      **One connection covers one project.** Console API keys are scoped to a single Statsig project, so a Statsig account with several projects needs a separate DSALTA connection for each — and DSALTA supports one Statsig connection per organization. Client and Server SDK keys cannot read the console API and are rejected.
    </Note>

    <Note>
      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.
    </Note>

    ## What DSALTA reads

    DSALTA reads the Statsig project user roster — names, emails and roles — which appears on your **Access** page; and the project's **feature gates** and **experiments**, which appear on your **Inventory** page with their status and, for gates, whether they are enabled. Evaluation logs and metrics are not read.

    It calls these Statsig Console API endpoints on `statsigapi.net`:

    * `/console/v1/users`
    * `/console/v1/gates`
    * `/console/v1/experiments`

    Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Statsig environment.

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection is rejected">
        The key must be a **Console API Key**, which starts with `console-`. A Client or Server SDK key authenticates flag evaluation only; it returns no users, and DSALTA refuses to connect on an empty roster. Create a Console API Key in the project you want reviewed and connect again.
      </Accordion>

      <Accordion title="The Access page shows the wrong project">
        The key decides the project. To review a different project, disconnect, create a Console API Key in that project, and connect again. Note that disconnecting permanently deletes the data already collected from Statsig.
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="How do I check whether the connection is healthy?">
        Open **Integrations** in the DSALTA sidebar, stay on the **Connected** tab, and click **Manage** on the integration's card. Open the **Status** tab: it shows either **Connected and working properly** or **Connection issues detected**.

        Use the **Status** tab, not **Overview** — Overview always reports **Connected** regardless of the real state.
      </Accordion>

      <Accordion title="A check shows Failed and nothing changed on my side">
        On an integration-powered check, **Failed** normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to **Source Data**, and read the result code: **403** is a missing permission, **428** is a setting DSALTA still needs, **500** is a failure on DSALTA's side.

        A real compliance gap shows **207** and leaves the test looking **Completed**. See [Understanding Test Results](/guides/compliance/test-results).
      </Accordion>

      <Accordion title="Data looks out of date">
        Compliance checks re-run once a day at 02:00 America/New\_York. To refresh sooner, open **Integrations → Connected** and click **Sync from integrations** at the top right — it refreshes every connected integration at once.
      </Accordion>

      <Accordion title="How do I repair a broken connection?">
        There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

        <Warning>
          **Disconnecting is destructive and cannot be undone.** DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see [Integration errors](/troubleshooting/integration-errors).
        </Warning>
      </Accordion>

      <Accordion title="Configure scope will not let me change anything">
        That is expected. **Configure scope** is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="How to connect">
    A Statsig Console API Key (console-…). The key is project-scoped — connect once per project. Read-only.

    **Before you begin**

    * A Statsig project, and **Admin** or **Owner** access to it, to create keys.

    You will need:

    | Field               | Where to find it                           | Example     |
    | ------------------- | ------------------------------------------ | ----------- |
    | **Console API Key** | **Project Settings → Keys & Environments** | `console-…` |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Statsig**, and click **Connect** to open the connect panel.
      </Step>

      <Step title="Create a Console API Key">
        In [console.statsig.com](https://console.statsig.com), open the project you want reviewed, go to **Project Settings → Keys & Environments** (the same page as [console.statsig.com/api\_keys](https://console.statsig.com/api_keys)), and create a **Console API Key**. Copy it — it starts with `console-`.

        <Warning>
          Do not use a **Client** or **Server** SDK key. Those cannot read the console API and are rejected. Note also that the key is scoped to this one project.
        </Warning>
      </Step>

      <Step title="Connect Statsig">
        Return to the connect panel, paste the Console API Key, and click **Connect**.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the key when you click **Connect**, by listing the project's users — a key that returns no users is rejected with a message pointing you to a Console API Key. On success the integration moves to the **Connected** tab, and **Manage → Status** reads **Connected and working properly**. Checks begin reporting after the first sync.
    </Check>

    <Warning>
      **If the connection is rejected.** An SDK key instead of a Console API Key, or a deleted key.

      The on-screen message is generic — see [Connection error messages](/troubleshooting/connection-error-messages).
    </Warning>
  </Tab>

  <Tab title="Automated checks">
    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.

    | Check                                                                                                                  | Severity | What it verifies                                                                   |
    | ---------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------------------------------------- |
    | [User access to Critical System should be valid](/integrations/statsig/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Statsig access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/statsig/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Statsig access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic       | Link                                                                              |
    | ----------- | --------------------------------------------------------------------------------- |
    | Setup       | [Console API introduction](https://docs.statsig.com/console-api/introduction/)    |
    | Remediation | [Project access management](https://docs.statsig.com/access-management/projects/) |
    | General     | [Statsig console](https://console.statsig.com)                                    |
    | DSALTA      | [Connection error messages](/troubleshooting/connection-error-messages)           |
  </Tab>
</Tabs>