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

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

## About

When you connect PagerDuty to DSALTA, the platform syncs your account users (email and role) and services using read-only API access. DSALTA compares the users on the PagerDuty Access page against your People directory, matched by email within your organization. The check passes when every PagerDuty user is an active employee on the People page. DSALTA evaluates this control on every sync.

## Why This Matters

Access to an incident-management tool like PagerDuty tends to accumulate over time as roles change, leaving people with more than they need. Excess or unauthorized 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, ISO 27001, HIPAA, and PCI DSS.

## How to Fix

**Before you begin**

* Ensure the PagerDuty integration is connected so DSALTA has the current list of users.
* Have **admin** or **owner** access to your PagerDuty account.

**Review PagerDuty access**

1. In **PagerDuty**, go to **People → Users** and review the list. Remove anyone who is not a current employee.
2. In **DSALTA**, go to **People** and confirm each PagerDuty user exists and is active.
3. For any user whose access is no longer appropriate, remove them in PagerDuty or correct their record on the People page.

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