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

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

## About

When you connect Aircall to DSALTA, the platform syncs your Aircall user roster using read-only API access. On every sync DSALTA compares the users on the Aircall **Access** page against your **People** directory, matched by email within your organization. The check passes when every Aircall user is an active employee on the People page.

## Why This Matters

Access to the organization's Aircall phone system must be limited to current, authorized employees. Access tends to accumulate over time as roles change, leaving people with more than they need. Excess access to a communications platform that can place calls and reach your customers on your behalf widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach it is a core control in SOC 2 and ISO 27001.

## How to Fix

**Before you begin**

* Ensure the Aircall integration is connected so DSALTA has the current list of users.

**Review Aircall access**

1. In Aircall, go to **Settings → Users** and review the users. Remove anyone who is not a current employee.
2. In DSALTA, go to **Data Library → Access**, filter for **Aircall**, and confirm each Aircall user maps to an active employee on the **People** page.
3. Mark each reviewed user as **In Scope** (valid) or **Not in Scope** (to be revoked), and record the reviewer.
4. Set a recurring access review schedule (quarterly is recommended).

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