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

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

## About

When you connect Clerk to DSALTA, the platform syncs your application users using read-only API access. DSALTA compares the users on the Clerk Access page against your People directory, matched by email within your organization. The check passes when every Clerk user is an active employee on the People page, and activates whenever a Clerk user cannot be matched to an active person.

## Why This Matters

Access to the organization's identity and authentication platform must be limited to current, authorized employees. Access tends to accumulate over time as roles change, leaving accounts that no longer map to a real, active person. Excess access widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach critical systems is a core control in SOC 2 and ISO 27001.

## How to Fix

**Before you begin**

* Ensure the Clerk integration is connected so DSALTA has the current list of users.
* Ensure you have access to the **Clerk Dashboard** with permission to manage users.

**Validate Clerk access**

1. In the **Clerk Dashboard**, open **Users** and ban or remove anyone who is not a current employee.
2. In DSALTA, open **People** and confirm each Clerk user exists and is active.
3. In DSALTA, go to **Data Library → Access** and filter for **Clerk** to review the matched users.
4. Set a recurring access review schedule (quarterly is recommended).

Once every Clerk 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 Clerk 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 the underlying configuration is fixed, 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 Clerk configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Clerk.
  </Accordion>
</AccordionGroup>