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

## What this check does

DSALTA compares the users on the Spacelift Access page against your People directory, matched by email, or by username when the username is not an email address within your organization. It passes when every Spacelift user is an active employee on the People page.

<Note>
  This check also runs on 115 other integrations — see [User access to Critical System should be valid](/tests/user-access-to-critical-system-should-be-valid) for the full list.
</Note>

<Info>
  Spacelift identifies managed users by username. When your identity provider issues usernames that are not email addresses, DSALTA matches the username against the People page's username field, then against the part of each email before the @.
</Info>

|               |                                                  |
| ------------- | ------------------------------------------------ |
| **Severity**  | Info                                             |
| **Category**  | `access`                                         |
| **Data used** | Spacelift Access page users, People page records |

**Passes when:** Every user with Spacelift access is an active employee on the People page.

## Why this matters

Access to the organization's infrastructure-automation platform must be limited to current, authorized employees.

## How to fix

**Review Spacelift users**

1. Sign in to Spacelift as an account **admin** or owner.
2. Hover over your name in the lower left, choose **Organization settings**, and open **Identity Management**. Each row is one managed user with their role and status.
3. Compare every user against your current employee roster, paying attention to any address on an external domain.
4. For anyone who should no longer have access, revoke their access from Identity Management. If access is granted through identity-provider group mapping or a login policy, remove them from the mapped group or update the policy as well.
5. For anyone over-permissioned, narrow the space roles assigned to them — **reader** where they only need to see stacks, and no **admin** role outside the spaces they operate.
6. In **DSALTA**, go to **People** and confirm every remaining Spacelift user maps to an active employee.

Once resolved, DSALTA records a **200** (compliant) result on this test's **Source Data** tab at the next scheduled run.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    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 **Compliance → Tests** and click **Run** in the **Run Test** row. You need Full Access to run a test on demand.
  </Accordion>

  <Accordion title="What does the status actually tell me?">
    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](/guides/compliance/test-results).
  </Accordion>

  <Accordion title="The check shows Failed. Does that mean I am non-compliant?">
    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**.
  </Accordion>

  <Accordion title="What if this check does not apply to us?">
    Deactivate it: open the test from **Compliance → 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](/guides/compliance/test-detail).
  </Accordion>

  <Accordion title="Does DSALTA change my configuration?">
    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.
  </Accordion>
</AccordionGroup>