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

## What this check does

DSALTA compares every GitGuardian workspace member on the Access page against your People directory, matching each one by email address. Pending invitations are not members and are not compared. A user with no matching person, or whose person is terminated or offboarding, is recorded with the reason.

<Note>
  This check also runs on 144 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>

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

**Passes when:** Every user on the GitGuardian Access page matches a person on the People page whose status is current and who is not in offboarding. An Access page with no synced GitGuardian users passes.

## Why this matters

Access to the organization's GitGuardian workspace, which watches its repositories for leaked secrets and holds every incident found, must be limited to current, authorized employees. An account on the GitGuardian Access page that belongs to nobody on the People page, or to someone who has already left, is access that no one is accountable for.

## How to fix

**Review GitGuardian workspace access**

1. Sign in to the [GitGuardian dashboard](https://dashboard.gitguardian.com) as the workspace Owner or a Manager.
2. Open **Settings → Workspace → Members**. Each row is one workspace member.
3. Compare every member against your current employee roster, paying attention to any address on an external domain and to any member with the Restricted access level.
4. Remove or deactivate anyone who is not a current employee.
5. In **DSALTA**, go to **People** and confirm every remaining GitGuardian member 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>