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

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

## About

When you connect Airtable to DSALTA, the platform syncs the connected account using read-only API access. On every sync DSALTA compares the users on the Airtable Access page against your **People** directory, matched by email within your organization, and activates this check when an Airtable user is not an active employee. It passes when every Airtable user is an active employee on the People page.

<Note>
  Airtable personal access tokens identify only their own owner, so the Access page lists the **connected account** rather than every individual person in your workspace. Confirm the connected account maps to a current, authorized employee, and review workspace or base sharing directly in Airtable.
</Note>

## Why This Matters

Access to the organization's Airtable data 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 database platform that can hold sensitive records 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 Airtable integration is connected so DSALTA has the current account and access data.
* Identify who has access by reviewing your workspace and base sharing settings in Airtable.

**Review Airtable access**

1. In **Airtable**, open the workspace or base **share settings** (or the **Admin panel** on Enterprise) and remove anyone who is not a current employee.
2. In DSALTA, go to **People** and confirm each Airtable user exists and is active.
3. Mark each reviewed account as valid or to-be-revoked, and record the reviewer.
4. Set a recurring access review schedule (quarterly is recommended).

Once every Airtable 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 Airtable integration is connected. You can also trigger a manual sync from **Integrations** in the sidebar.
  </Accordion>

  <Accordion title="Why does the Access list show only the connected account?">
    Airtable personal access tokens can read only their own identity, so DSALTA lists the connected account instead of a full member roster. A full roster requires an Airtable Enterprise account with additional scopes. Review workspace and base sharing directly in Airtable.
  </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 Airtable configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Airtable.
  </Accordion>
</AccordionGroup>