Two-way sync overview (Beta/Limited availability)
  • 29 Mar 2023
  • 9 Minutes to read
  • Dark

Two-way sync overview (Beta/Limited availability)

  • Dark

Two-way sync is only available to a limited number of customers. We welcome your feedback about this feature here.

Two-way sync allows existing records to be edited in one or more destinations and synced back to a single-source-of-truth table. This article covers configuring an ecosystem of bases and interfaces so multiple teams can have the most up-to-date information. Using two-way sync helps to prevent data silos and other inefficiencies in today’s hybrid work environment.


Plan availabilityCurrently in limited beta availability
  • Owners/Creators - Can create, modify, delete, and run syncs in the base(s) they have access to.
  • Editors - Edit records in source or destination bases that they have access to as base or workspace collaborators. Additionally, editors can manually run syncs in the destination base(s) to which they have access.
Platform(s)Web/Browser, Mac app, and Windows App 
Related reading
  • Sync overview - For more information on general feature behavior and plan limits.
  • Airtable Sync - Basic setup - If you've never interacted with the Airtable Sync feature before, then it's important to read this article first to learn the basics.
  • Sync permissions - General information about how permissions relate to Airtable Sync.
Airtable terminology
  • Source - A single-source-of-truth dataset that is synced elsewhere in Airtable. You can think of this as the master dataset.
  • Destination - A table that has been set up to sync with the source. An indirect relationship with other destinations is also established when setting up a two-way sync. Interfaces in destinations can be set up to permit edits that will sync back to the source.

Understanding Two-way sync

A two-way sync will always have a single source table where the initial sync share view is created. Edits made in one or more destination tables or interfaces in other bases will sync back to the source table. To illustrate how the two-way sync schema works consider the image below. 

There are two overarching concepts worth digesting before moving on:

  • The black two-sided arrows represent the direct connection between a source table and its destination(s).
  • The lighter grey and dotted line arrows represent the indirect relationship between destinations. Changes made in a destination will first sync back to the source before pushing to other destinations upon the next sync. 
It’s only possible to add new records in a source base. At this time, destinations with two-way sync turned on are only able to edit records created in the sync source. We cover this and other limitations below.

Two-way sync source view configuration

To start, navigate to a grid view of the information you are wanting to enable syncing. click Share view and click Create a shareable grid view link. Then, enable both:

  • Allow data in this view to be synced to other bases
  • Allow edits from other bases

There are two options below this toggle to consider:

  • All editable fields - All editable fields in the source table will be editable in the destination table. Additionally, editable fields added in the source table will be editable in any destination tables in the future.
  • Specific fields - Only certain fields in the source will be available for syncing.

An editable field is any field within a table that is not locked. As a reminder, individual field-level editing permissions can be set across the view you are using as the sync source. We cover more on permissions and Two-way sync here

Two-way sync destination configuration

If you are looking to adjust a previously configured sync to have two-way sync enabled, you’ll want to click the drop-down next to the table’s name. Then, select the “Update sync configuration” option and toggle the preferred editing access level discussed further in this section.
Step 1: Begin setting up the destination

In another base, you can follow the normal flow of adding a new table that will sync with the source table that has been configured. Click the plus sign and choose Sync data from Airtable base.

Step 2: Choose a source that has two-way syncing enabled

From here, you can either select a view from a base that you collaborate in or use a sync share link that has been shared with you. In either case, the source view you are syncing with must have two-way sync enabled to edit information in the destination table.

Step 3: Select which fields to sync

Click Next and then choose which fields, All fields or Specific fields, you would like to sync over from the source to this destination table. Even though you might be able to see a field in the destination table, it doesn’t necessarily mean that it will be editable. Editability is dependent upon the configuration made in the source as well as an upcoming step in the destination sync’s setup.

Under the “Advanced” section, you can choose which field from the source you would like to set as the primary field in this destination table. By default, the primary field will match the source table’s primary field. More information about this option is available here.

Once the field selections have been set, click Next to move onto the final setup screen.

Step 4: More configuration options

Before creating your synced table, there is a setting that allows you to choose who can edit source records. Click Change below the Edit source records toggle to make adjustments based on your needs. This option is specific to the two-way sync feature.

It’s possible that not all of the workspaces that you collaborate in will have two-way sync functionality. If you don’t see the option to set who can edit source records, then it’s likely the case that the destination base you are trying to create the two-way sync in resides inside a workspace that does not support this feature currently.

There are three options available for source editing:

  1. Allow creators and above in this base to edit source records
  2. Allow editors and above in this base to edit source records (Default)
  3. Don't allow anyone in this base to edit source records

Two-way sync permissions have many considerations, we recommend consulting this article to dig into permissions dependencies more deeply.

The other two options in this section should not be changed. Changing the sync frequency to Only sync changes when requested or the record deletion option to Leave the records in this table will cause two-way syncs to break and render as a one-way sync. 
Step 5: Create the table

Once you’ve selected your desired settings, click Create table. It’s a good idea to check that the functionality of the table matches your expectations. If you need to adjust any parameters of this synced destination table, then click the drop-down next to the table’s name and select the Update sync configuration option.

Two-way syncing in interfaces

Once a table with two-way sync enabled has been set up following the steps listed in the section above, interfaces can be configured to allow edits to be made from an interface page. These edits will sync back to the source just like edits made in a destination table. There are two general interface surfaces where two-way syncing can be enabled:

  1. Visualization layouts - These layout types offer quick configuration options and an experience similar to views in Airtable bases.
  2. Interface elements - The following interface elements support two-way syncing: Grid, Record detail, Calendar, Kanban, Timeline, Gallery, List, and Record picker.
Enabling two-way sync editability in visualization layouts

There are two surfaces within visualization layouts that allow end-users to edit records. You can choose to use one of these options independently, or both of these options together:

  1. Click into record details - Setting up this option allows end-users to open up more details for a specific record. Builders can customize this record detail page as a sidesheet or fullscreen experience. Each field that you want end-users to be able to edit will need to be configured individually. From the customization screen for the record detail page, click a field that you want to make editable. Under the Permissions section change the setting to Editable.
    If you see a message that "This field is synced from a source that doesn't allow it to be edited," then there are likely field editing permissions in the source base preventing the field from being set as Editable.
  2. Edit records inline - You can choose to also make inline editing possible for all available fields from the source. To do this click on the Edit records inline option and then toggle on the option that appears in the settings.
Enabling two-way sync editability for supported interface elements

Individual interface elements can be set as editable as well. Under Permissions, choose the Editable option to allow editing for all available field from the source. In certain elements, like the record picker element, you can also choose to allow records to be edited. However, to accomplish this, each field that you want end-users to be able to edit will need to be configured individually. Click each field to change it's Permissions settings to Editable.


We cover these limitations in more detail as well as dependencies and best practice considerations in a separate article.

  • Edits (two-way syncs) are not allowed in Gantt views.
  • New records cannot be added from a destination base.
  • Linked record, user, and attachment fields are not editable.
  • Linked record and user fields sync as text fields.
  • Button, formula, and other computed field types are not available for syncing purposes since they can rely on information that is unavailable in destinations.
  • Fields that are added, or customizations to fields (e.g., adding a select field option) in a destination table will not sync back to the source.
  • Two-way sync sources containing more than 200k cells (e.g. 10k records x 20 fields) are not available.
  • Sync may take a few minutes to propagate in both directions.
  • Edits cannot be made using automations, API calls, or the mobile app in destinations.


How often does synced information update?

Changes to the source table will usually take a few minutes to sync to a destination table with automatic syncing turned on. Destination bases with manual sync turned on will need to be synced manually for changes to appear.  When a change is made in the destination table, it will sync with the source table in close to real-time.

Is there a limit on which sync sources can be used for two-way syncs?

Yes. Views containing more than 200,000 cells (e.g. 10k records x 20 fields) are not available for use as a two-way sync source.

Will the person who made the edit appear in the record activity log?

Just as with one-way sync, in the destination table, any changes will be attributed to “Table Sync.”

Can I build an interface that allows edits in the destination?
If I add a field in the destination, will it appear in the source?

No, just like in one-way sync, that field will appear in and be owned by the destination base.

If I edit a field’s configuration in the destination (e.g., adding a select field option), will it be reflected in the source?

Field type customizations are specific to the destination base and won’t apply to source bases.

Can linked records be edited/clicked into in the destination?

No. Linked records are converted into unlinked, non-editable text fields in destination bases.

Can I create a record in a destination table?

No, records can only be created in the source table.

Was this article helpful?