Airtable
Connect Airtable to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Airtable to collect ticketing evidence with automated compliance tests, switched on per workspace.
| Category | Ticketing |
| Connect with | API token, MCP server |
| What a connection produces | Automated compliance tests |
| Airtable's guide | airtable.com |
Connect with an API token
-
In Airtable:
- Sign in to Airtable as an enterprise admin and open the personal access tokens page (airtable.com/create/tokens).
- Click Create new token and give the token a unique name (for example Safeguard).
- Choose the scopes enterprise.account:read and enterprise.user:read. These enterprise admin scopes are available only to administrators of enterprise accounts.
- Create the token and copy it; Airtable shows it only once.
Airtable shows the secret only once, so copy it before you leave the page.
Airtable's public documentation does not cover every step.
Needs Airtable's Enterprise Scale plan. Enterprise admins can also create a token for a service account from the Admin Panel. The fetched pages don't show how the token is given access to the enterprise account (only 'add a base' for bases) or where the Admin Panel shows the enterprise Account ID.
Source: airtable.com, airtable.com, checked 2026-10-07.
The permissions Safeguard needs:
enterprise.account:read,enterprise.user:read. Needs Airtable's Enterprise Scale plan. Safeguard's compliance tests for Airtable need the credential on the API token tab: an OAuth connection cannot read everything they check. -
On Compliance › Connectors, open Airtable, click Connect, choose API token and fill in:
Field What to enter Account ID Required. Access token Required. Stored encrypted and never shown again. -
Click Connect with token.
Connect with the MCP server
Choose MCP server: the address https://mcp.airtable.com/mcp is filled in. Sign in to Airtable when asked. It lets Griffin AI search Airtable; the compliance evidence comes from the API token connection.
Frameworks
Safeguard's automated tests read Airtable and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC6.1, CC6.2, CC6.3 | 4 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2, A.8.5 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(d) | 4 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5, 8.4.2 | 4 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-03, PR.AA-05 | 4 |
These tests are switched on per workspace by the Safeguard team.
Related
- Ticketing connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks