Skip to main content

​
What this check does

DSALTA compares the users on the Airtable Access page against your People directory, matched by email within your organization. It passes when every Airtable user is an active employee on the People page.
This check also runs on 85 other integrations — see User access to Critical System should be valid for the full list.
Passes when: Every user with Airtable access is an active employee on the People page.

​
Why this matters

Access to the organization’s Airtable data must be limited to current, authorized employees.

​
How to fix

Review Airtable collaborator access
  1. Sign in to Airtable and open the workspace from the left sidebar.
  2. Click the workspace name and choose Share to open Workspace collaborators. On Enterprise plans, use Admin panel → Users for the org-wide list.
  3. Compare every collaborator against your current employee roster, paying attention to any address on an external domain.
  4. For anyone who should no longer have access, open the permission dropdown beside their name and choose Remove access.
  5. For anyone over-permissioned, use the same dropdown to change Owner or Creator down to Editor, Commenter, or Read only.
  6. Repeat on each base’s Share → Base collaborators list to catch base-level invites that bypass the workspace.
  7. In DSALTA, go to People and confirm every remaining Airtable collaborator maps to an active employee.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.