How to Audit Your Airtable Environment Before the Acquisition Closes

The proposed Bending Spoons acquisition has given many companies a reason to look more closely at how Airtable is being used across their business.

That does not mean organizations need to prepare for an immediate migration. The transaction is still expected to close by the end of 2026, subject to regulatory approval. Until then, Airtable continues to operate independently.

A better use of this period is to conduct an Airtable audit.

Over time, Airtable environments naturally become more complicated. A base created for one team may become part of a company-wide process. New automations get added, integrations connect additional systems, employees change roles, and temporary workspaces become permanent.

An Airtable system audit helps you understand what you actually have before deciding what needs to be improved.

Start With Your Business-Critical Bases

Not every base deserves the same level of attention.

Begin by identifying the Airtable systems your business would struggle to operate without. These may include customer delivery, sales operations, project management, marketing workflows, approvals, resource planning, finance processes, or executive reporting.

For each critical base, document:

· What the base is used for

· Which team owns it

· Who manages it technically

· Which departments depend on it

· What happens if it becomes unavailable

· Whether the process is documented elsewhere

This gives your Airtable workspace audit a business context. The goal is not simply to count bases. It is to understand which ones matter.

Review Workspace and Base Ownership

Ownership is one of the easiest areas to overlook.

Airtable recommends that larger teams have two workspace Owners so management can continue if one owner becomes unavailable or leaves the company. Workspace Owners also have access to all bases within that workspace.

During your audit, look for:

· Workspaces with only one owner

· Bases owned or managed by former employees

· Critical systems dependent on one person

· Workspaces with unclear business ownership

· Bases created outside the intended organizational structure

Airtable provides specific processes for transferring workspace, base, and interface ownership when employees leave an organization.

If an important system depends on one individual, that is a continuity risk regardless of the acquisition.

Audit Users and Permissions

Permissions often become messy as an Airtable environment grows.

Airtable permissions control what users can view and edit across workspaces, bases, Interfaces, and administrative areas.

An Airtable permissions audit should identify:

· Former employees who still have access

· External collaborators who no longer need access

· Users with higher permissions than necessary

· Shared Interfaces that are no longer required

· People who can edit data when read-only access would be enough

· Uncontrolled workspace or base invitations

Business and Enterprise administrators can manage user access and permissions through Airtable’s admin tools, including removing access and transferring ownership.

This review can improve both security and license management.

Check Your Airtable Automations

Automations are often where hidden technical debt builds up.

A business process may appear straightforward to users while several automations are working behind the scenes to update records, send notifications, create tasks, or connect external systems.

During an Airtable automation audit, identify:

· Which automations are active

· What each automation does

· Who created it

· Which external accounts it uses

· What happens if it fails

· Whether duplicate automations exist

· Whether anyone still understands the logic

Airtable currently allows Owners and Creators to configure and manage automations, while Editors have more limited visibility and control.

Pay particular attention to automations connected to individual employees' accounts. A workflow that depends on someone's personal credentials can become a problem when that person changes roles or leaves the company.

Map Your Airtable Integrations

Airtable rarely operates completely on its own.

Your environment may exchange data with CRM systems, project-management tools, finance applications, calendars, automation platforms, internal databases, or custom applications.

Create a simple Airtable integration audit showing:

· The system connected to Airtable

· What information moves between the systems

· Whether the connection is one-way or two-way

· Who owns the integration

· Which account authenticates it

· Which business process relies on it

Airtable Sync, for example, can move records from source systems or bases into destination tables, and changing permissions or share-link restrictions can sometimes interrupt existing syncs until they are reconfigured.

Knowing these dependencies makes troubleshooting easier and gives you a clearer picture of how deeply Airtable is embedded in the business.

Review Personal Access Tokens and Credentials

Credentials deserve their own part of the audit.

Airtable Personal Access Tokens can be limited to specific scopes and bases, but they can also be configured with access across multiple workspaces and resources.

Review:

· Who owns each Personal Access Token

· Which bases it can access

· Which permissions or scopes it has

· Which integration uses it

· Whether the access is broader than necessary

· Whether unused tokens can be removed

A good principle is to give integrations only the access they actually need.

This reduces the risk created by forgotten credentials and makes future system changes easier to manage.

Look at Your Data Structure

Not every Airtable problem is related to access or integrations.

Many environments simply become difficult to maintain because the underlying structure has grown without a clear plan.

During your Airtable architecture review, look for:

· Duplicate tables

· Duplicate records

· Unnecessary fields

· Overly complex formulas

· Multiple sources of truth

· Poor naming conventions

· Excessive linked-record chains

· Separate bases storing the same information

Ask a simple question: If someone new joined the company tomorrow, could they understand how this system is structured?

If the answer is no, documentation and simplification should become priorities.

Review Interfaces and External Access

Interfaces may expose only part of a base to particular users, which is useful for simplifying how teams interact with Airtable.

However, access should still be reviewed.

Airtable allows different ways of sharing Interfaces, including interface-only access on qualifying paid plans. Business and Enterprise Scale administrators also have additional tools for managing Interface access.

Check whether:

· Existing Interface users still need access

· External collaborators are appropriate

· Published Interfaces are still being used

· Access matches the user's role

· Sensitive information is exposed unnecessarily

This is particularly important when Airtable is used with clients, suppliers, contractors, or other external users.

Check Documentation and Continuity

A technically strong system can still be risky if nobody knows how it works.

Every important Airtable environment should have basic Airtable system documentation covering its purpose, ownership, integrations, automations, major tables, important dependencies, and recovery procedures.

Also review what historical information is available. Airtable provides record-level revision history, although retention and available history depend on the plan and changes imported through external syncs may not appear in the same way as direct record edits.

The aim is not to document every field. Focus on the information someone would need to understand, maintain, and recover a critical workflow.

What Does a Healthy Airtable Environment Look Like?

A healthy environment does not need to be perfectly simple.

It should, however, be understandable and controlled.

You should be able to answer:

· Which bases are business-critical?

· Who owns them?

· Who has access?

· Which automations are running?

· Which systems are integrated?

· Who owns the credentials?

· Where is the source of truth?

· What would happen if a key employee left?

· Is the system documented?

If these questions are difficult to answer, the audit has already identified areas worth improving.

Conclusion

The period before the Airtable acquisition closes is a good opportunity to understand the health of your existing environment.

An Airtable audit is not about preparing to leave the platform. It is about reducing avoidable risk.

Review ownership, permissions, Airtable automations, integrations, Personal Access Tokens, data structure, Interfaces, and documentation. Identify systems that rely too heavily on one person and workflows that have become unnecessarily complex.

Whatever happens after the acquisition, a cleaner and better-documented Airtable environment will be easier to manage, optimize, scale, or migrate if that decision ever becomes necessary.