Skip to main content
Connect your Airtable Enterprise account to Oleria to gain continuous visibility into who has access across your workspaces and bases, and to review activity across your Airtable enterprise. Oleria reads identity, access, and audit data from the Airtable Enterprise Admin API, so you can see every account, group, role, and access change in one place. This page provides step-by-step guidance for connecting Airtable to Oleria.

​
What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from your Airtable enterprise:
  • Accounts - enterprise users and service accounts, including admin status, license type, and activity status.
  • Groups - enterprise user groups and their membership.
  • Roles and permission levels - the five Airtable permission levels (read, comment, edit, create, owner), modeled as roles, with effective access resolved across direct, group, and workspace-inherited collaboration.
  • Resources - workspaces and bases, and the collaborators and groups with access to each.
  • Audit activity - enterprise-wide audit log events such as user creation, permission changes, and login activity, covering a 180-day retention window.
Oleria does not currently discover access granted via Airtable share links (public or link-based sharing of a base or view), and does not inventory Airtable personal access tokens or OAuth integrations as non-human identities - Airtable’s enterprise API exposes no endpoint to enumerate them. Airtable service accounts are discovered and appear as accounts. Activity performed by PATs or OAuth integrations still appears in audit events. If your enterprise relies on share links or on PAT-based automation, that access will not appear in Oleria’s inventory.

​
Prerequisites

  • Airtable Enterprise Scale plan - the Enterprise Admin and Audit Log API is not available on other plans
  • Enterprise admin access in Airtable
  • Your Airtable Enterprise Account ID, found in the Airtable admin panel

​
Choose an authentication method

Oleria supports two ways to connect to Airtable. Choose the one that fits your organization:
Both authentication methods can perform discovery and remediation - OAuth requests the full scope set automatically, including enterprise.user:write. This scope is optional: if it isn’t granted (denied during the OAuth consent screen, or omitted when creating a Personal Access Token), the connection still works normally for discovery - only remediation actions are unavailable, and only surface as a permission error if one is attempted. On Airtable’s OAuth consent screen, every requested scope appears as an individually deselectable checkbox, but enterprise.user:write is the only one safe to deselect - denying any of the other requested scopes will cause the connection to be rejected.
If you’re using OAuth, skip ahead to Connect Airtable to Oleria - no token needs to be created in Airtable first.

​
Create a Personal Access Token in Airtable

Only needed if you’re connecting with a Personal Access Token rather than OAuth.
1

Open personal access tokens in Airtable

Sign in to airtable.com and go to Builder Hub -> Personal access tokens.
2

Create a token with the required scopes

Create a new token and give it a recognizable name such as Oleria connector. Grant the following scopes:
The enterprise.user:write scope is only required if you want Oleria to take remediation actions. Omit it for read-only discovery.
3

Copy your Enterprise Account ID and token

Copy and save the following values - you will need them when connecting in Oleria:
  • Enterprise Account ID - found in your Airtable admin panel URL. It starts with ent (for example, entXXXXXXXXXXXXX).
  • Personal Access Token - the token value shown when you create the token.
The token value is shown only once. Store it securely - if you lose it, you must create a new token and update the connection in Oleria.

​
Connect Airtable to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations -> select Airtable.
2

Choose an Authentication Method

Select OAuth (recommended) or Personal Access Token from the Authentication Method dropdown. The fields below change depending on which you choose.
3

Complete the connection form

4

Connect

Select Connect to Airtable.
  • If you selected OAuth, you’re redirected to Airtable to sign in and approve the requested scopes. After you approve, you’re returned to Oleria and the integration is created automatically.
  • If you selected Personal Access Token, the integration is created immediately using the token you pasted.

​
Verify the integration

Confirm the Airtable instance appears in your Oleria workspace connected integrations. After the first sync completes, you can review the discovered accounts, groups, roles, resources, and activity in your Oleria workspace.
If you connected with OAuth, Oleria refreshes your access automatically - no action is needed on your part. If you revoke Oleria’s access from within Airtable, discovery stops until you reconnect.If you connected with a Personal Access Token, update the token in Oleria by editing the integration whenever you rotate it in Airtable. An expired or revoked token will cause discovery to stop.

​
Remediation actions

Beyond discovery, Oleria can act on Airtable access to remediate risk. The following actions are supported:
Remediation requires the enterprise.user:write scope. OAuth connections request this automatically. A Personal Access Token created without this scope can still perform discovery but will return a permission error when an action runs.
Oleria’s Airtable integration governs enterprise-level access only. Adding, removing, or updating a user’s collaborator permissions on a specific workspace or base is not yet supported as a standalone remediation action. The one exception is Remove User from Enterprise, which cascades to every workspace and base the user could access.

​
Contact us

For questions about this integration, contact us at support@oleria.com.