> ## 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 users with access to critical systems are authorized in Vercel.

Checks that users with access to critical systems are authorized in Vercel.

## About

When you connect Vercel to DSALTA, the platform syncs your account owner and team members using read-only API access. DSALTA lists the Vercel account owner and each team member with their role and checks them against the allowed members. DSALTA evaluates this control on every sync, and activates this check when someone holds access who should not.

## Why This Matters

Access to a critical hosting platform must be restricted to authorized people. Access tends to accumulate over time as roles change, leaving people with more than they need. 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, ISO 27001, and HIPAA.

## How to Fix

**Before you begin**

* Ensure the Vercel integration is connected so DSALTA has the current list of members.
* Ensure you have **admin** access to the Vercel account or team.

**Review Vercel team access**

1. In DSALTA, go to **Data Library → Access** and filter for **Vercel**.
2. Review each member's role against their current job function.
3. In **Vercel → Team settings → Members**, remove unauthorized members or adjust their roles.
4. In DSALTA, mark each reviewed member as **In Scope** (valid) or **Not in Scope** (to be revoked), and record the reviewer.
5. Set a recurring access review schedule (quarterly is recommended).

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