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

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

## About

DSALTA compares the users on the Stripe Access page against your People directory, matched by email within your organization. It passes when every Stripe user is an active employee on the People page. The check evaluates on every sync while the Stripe integration is connected.

<Note>
  **What you'll see.** Stripe exposes no member-list API, so the Access page shows the connected account owner as a single row rather than individual dashboard members. Confirm this owner is a current employee; email-matched results may need manual review.
</Note>

## Why This Matters

Access to the organization's payment platform must be limited to current, authorized employees. Access tends to accumulate over time as roles change, widening your attack surface and breaking the principle of least privilege. Regularly validating who can reach critical systems is a core control in SOC 2, ISO 27001, and PCI DSS.

## How to Fix

**Before you begin**

* Ensure the Stripe integration is connected so DSALTA has the current account owner.
* Ensure you have access to **Settings → Team and security** in the Stripe Dashboard.

**Review Stripe access**

1. In the **Stripe Dashboard**, go to **Settings → Team and security** and remove anyone who is not a current employee.
2. In DSALTA, go to **People** and confirm each Stripe user exists and is active.

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