> ## 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 everyone with OpenAI access is an active employee on the People page.

Checks that everyone with OpenAI access is an active employee on the People page.

## About

When you connect OpenAI to DSALTA, the platform syncs your organization members using read-only API access. On every sync DSALTA compares the users on the OpenAI Access page against your **People** directory, matched by email within your organization, and activates this check when an OpenAI user is not an active employee on the People page.

<Note>
  DSALTA reads organization members through the OpenAI Organization (Admin) API. If a non-admin key is connected, only the connected account owner is visible, so the email-based match may not resolve automatically. Use the Access list to confirm each OpenAI user is a current, authorized employee.
</Note>

## Why This Matters

Access to the organization's AI platform must be limited to current, authorized employees. Access tends to accumulate over time as roles change, leaving people with more than they need. Excess access to an AI platform that can process sensitive data widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach it is a core control in SOC 2, ISO 27001, and the EU AI Act.

## How to Fix

**Before you begin**

* Ensure the OpenAI integration is connected with an admin key so DSALTA has the current list of organization members.

**Review OpenAI access**

1. In OpenAI, go to **Settings → Organization → Members** and remove anyone who is not a current employee.
2. In DSALTA, go to **People** and confirm each OpenAI user exists and is active.
3. In **Data Library → Access**, filter for **OpenAI** and confirm each user maps to an active employee on the **People** page.
4. Mark each reviewed user as **In Scope** (valid) or **Not in Scope** (to be revoked), and record the reviewer.
5. Set a recurring access review schedule (quarterly is recommended).

Once every OpenAI user is an active employee on the People page, DSALTA retrieves the change on the next sync and 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 OpenAI 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 every OpenAI user maps to an active employee, 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 OpenAI configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in OpenAI.
  </Accordion>
</AccordionGroup>