Skip to main content

​
Overview

DSALTA connects to Airtable using read-only API access to collect compliance evidence automatically. Data syncs every 24 hours and feeds into your Data Library modules.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Airtable account.
What you’ll see. Airtable personal access tokens identify only their own owner, so DSALTA’s Access page lists the connected account (by email), not every individual person in your Airtable workspace. A full member roster requires an Airtable Enterprise account with additional scopes. Treat the Access list as the connected account and confirm its owner against your People page. DSALTA’s Inventory page lists the bases the token can read.

​
How to Connect

Airtable connects with a personal access token (PAT) — there’s no app to install.
1

Open Airtable token creation

Go to airtable.com/create/tokens and create a personal access token. A free Airtable account works — no paid or enterprise plan is required.
2

Add the required scopes

In the Scopes section, add both of these scopes: user.email:read (identifies the connected account on the Access page) and schema.bases:read (lists your bases on the Inventory page). Optionally add data.records:read only if record-level checks are needed.
3

Grant base access

In the Access section, add the base(s) or workspace(s) you want DSALTA to read. This is required — the token can see no bases until you add them here, and the Inventory page stays empty otherwise.
4

Copy the token

Create the token, then copy it (it starts with pat).
5

Connect

In the DSALTA sidebar, go to Integrations, find Airtable, and click Connect. Paste the token in the secure window and submit.
6

Finish

DSALTA runs an initial sync — usually a few minutes — after which the compliance checks below activate.

​
Automated Compliance Checks

Each check below runs automatically every 24 hours. Click any check for step-by-step remediation guidance.

​
Troubleshooting

Re-authenticate from Integrations → Airtable → Reconnect. This can happen if the personal access token was deleted, expired, or had its scopes changed in Airtable.
Confirm the personal access token is still valid and still carries the user.email:read and schema.bases:read scopes. If the Inventory page is empty, check that the base(s) or workspace(s) are still added to the token’s Access section, then trigger a manual sync from the integration settings.