https://api.airtable.com/v0), using a personal access token (or a service account token on Enterprise Scale). Configview sends only GET requests. It never creates, changes or deletes anything in Airtable, and it never reads the records in your bases.
You will end up with 1 required secret (AIRTABLE_TOKEN) and 1 optional secret (AIRTABLE_ENTERPRISE_ACCOUNT_ID) in Configview when setup is complete.
Scope of this integration today. Configview answers “who can build in Airtable and what can they reach”: every base with its workspace, collaborators, groups and pending invites; table and field names and types; workspace invite and share restrictions; and webhook destination hosts. On Enterprise Scale it also reads the user directory (admin, SSO and two-factor flags, last activity), user groups, share links with their state and password protection, and the audit log. It does not read records, cell values, select-field options, attachments, comments, webhook payloads, share link addresses or invite link addresses.
What you need
- An Airtable account that is an owner or creator of the workspaces you want covered
- For the enterprise collectors: an Enterprise Scale plan and an enterprise admin (or an enterprise service account) to create the token
Step 1: Open the Airtable page in Configview
Open Configview in a second browser tab and leave it open:https://{companyname}.configview.com/admin/integrations/airtable
Step 2: Create the token
- In Airtable open Builder hub > Personal access tokens and choose Create token (
https://airtable.com/create/tokens) - Name it
Configview - Add these scopes:
schema.bases:readworkspacesAndBases:read- Optional:
webhook:manage. Airtable has no read-only webhook scope, so this scope also allows changes. Configview only lists webhooks and never creates, changes or deletes one, or fetches payloads. Leave it off for a read-only token; the webhooks collector then skips.
- Enterprise Scale only, also add:
enterprise.account:readenterprise.user:readenterprise.groups:readenterprise.auditLogs:read- Optional:
workspacesAndBases.shares:manage. It is the only scope that lists share links, and it also allows changing them. Configview only lists them. Leave it off for a read-only token; the share-links collector then skips.
- Under Access, add every workspace or base you want covered. A token only sees what it is granted. On Enterprise Scale, add the enterprise account.
- Do not add any
data.recordsscope. Configview never needs it. - Create the token and copy it; Airtable shows it once
- In the Configview tab paste it into
AIRTABLE_TOKENunder Credentials and save
Step 3: Enterprise account ID (optional)
Only on Enterprise Scale. Copy your enterprise account ID (it starts withent) from the Airtable admin panel and save it as AIRTABLE_ENTERPRISE_ACCOUNT_ID. Leave it empty and the collectors marked Enterprise below skip cleanly.
Step 4: Connect and verify
- Click Connect. Configview creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads the secret, lists bases, and reads the enterprise account if its ID is set.
- 401. The token is wrong, revoked or expired.
- 403 or 404. The token lacks a scope, or does not have access to that base or the enterprise account.
Data Tables
Each snapshot table has arun_at column and keeps only the newest run. airtable_audit_logs is a ledger: it keeps every event it has read.
Things worth knowing
A token only sees what it was granted. The base list, the schema and the collaborators all depend on which workspaces and bases you added to the token. Bases that are missing from Configview were most likely not added to the token. Access through a group.airtable_collaborators lists people and groups added directly. Members of a group appear in airtable_group_members (Enterprise), not as collaborators, so the real number of people with access to a base is higher than the direct counts.
Effective access to a base is its own collaborators plus the collaborators of its workspace.
Enterprise-only data. Users, groups, share links and the audit log exist only on Enterprise Scale. Without the enterprise account ID those collectors skip, and the related questions return nothing.
No list-all endpoints for users and groups. Airtable returns user and group ids on the enterprise account, and Configview then fetches each one. Configview asks for users 100 ids at a time; Airtable’s reference states no maximum, so confirm the first run returns every user.
Share and invite links are never stored. A share link or invite id works as a key into the base, so Configview keeps only a short one-way hash to tell links apart.
Audit log. The first run reads the last 30 days (Airtable keeps 180); later runs only fetch what is new. Event payloads, which can describe record and field changes, and user agents are not kept. The shape of the actor object is not fully spelled out in Airtable’s reference, so check on the first run that actor emails are filled in.
Rate limit. Airtable allows 5 requests per second per base and 50 per second per token, and answers HTTP 429 and refuses all requests for 30 seconds beyond that. Configview paces itself at 150 requests a minute per script and waits 30 seconds on a 429.
What isn’t collected
- Records, cell values, comments, attachments and the contents of views
- Select-field options, formulas and table or field descriptions
- Share link and invite link addresses (only a one-way hash)
- Webhook URLs (only the host) and webhook payloads
- Audit log payloads and user agents