> ## 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 every user with Auth0 access is an active, authorized employee.

Checks that every user with Auth0 access is an active, authorized employee.

## About

Access to the organization's Auth0 tenant must be limited to current, authorized employees. DSALTA compares the users on the Auth0 Access page against your People directory, matched by email within your organization. The check passes when every Auth0 user is an active employee on the People page. DSALTA evaluates this control on every sync using read-only Management API access.

## Why This Matters

Your Auth0 tenant controls who can manage identity for your applications, so any account that does not belong to a current, authorized employee is an unmonitored path into critical systems. Regular validation of who holds access — and removal of accounts that should not — is required by access-control frameworks including SOC 2, ISO 27001:2022, HIPAA, and PCI DSS v4.0.1, and supports least-privilege and periodic access reviews.

## How to Fix

**Before you begin**

* Ensure you have **administrator** access to the Auth0 Dashboard.
* Have your People directory (or HRMS) available to confirm who is a current employee.

**Review Auth0 access**

1. In the **Auth0 Dashboard**, go to **User Management → Users** and review the users. **Block** or **delete** anyone who is not a current employee.
2. In **DSALTA**, open **People** and confirm each Auth0 user exists and is active.

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