--- title: "Airtable sync permissions" slug: "sync-permissions" description: "Similar to other surfaces throughout Airtable, you'll want to consider permissions settings when enabling sync for a shared view. Learn about these considerations in this article." updated: 2026-02-19T18:42:03Z published: 2026-02-19T18:42:03Z --- > ## Documentation Index > Fetch the complete documentation index at: https://support.airtable.com/llms.txt > Use this file to discover all available pages before exploring further. # Airtable sync permissions # Airtable sync permissions | [Plan availability](https://airtable.com/pricing) | Team, Business, and Enterprise Scale plans | | --- | --- | | [Permissions](/docs/permissions-overview) | - **Owner/Creator** – Can perform all sync actions, including creating and configuring synced tables and share links. - **Editor** – Can create syncable view share links and manually trigger syncs. Cannot create or delete synced tables or modify sync configurations. - **Commenter/Read-only** – Cannot create synced tables directly. Must be given a share link by an Editor or higher to initiate a sync from a source they do not have edit access to. | | Platform(s) | Web/Browser, Mac app, Windows app, and mobile apps | | Related reading | - [Airtable permissions overview](/docs/airtable-permissions-overview) - [Airtable base permissions](/docs/base-permissions) - [Getting started with Airtable sync](/docs/getting-started-with-airtable-sync) - [Two-way syncing in Airtable](/docs/two-way-syncing-in-airtable) - [Using field and table editing permissions](/docs/using-field-and-table-editing-permissions) - [Protecting share links on a base](/docs/protecting-share-links-on-a-base) | --- ## General sync actions > [!CAUTION] > Note > > Setting or changing permissions (such as passwords or domain restrictions on a syncable share link) can cause existing synced tables to stop syncing. Affected synced tables will need to be reconfigured to resume. | Action | Owner/Creator | Editor | Commenter | Read-Only | | --- | --- | --- | --- | --- | | Create and remove syncable view share links | ✅ | ✅ | | | | Manually sync ("Sync now") | ✅ | ✅ | | | | Create and delete synced tables | ✅ | | | | | Update sync configurations | ✅ | | | | | Choose shared views when setting up a synced table (source base must have Editor permissions or higher) | ✅ | ✅ | | | --- ## Share link restriction scenarios > [!CAUTION] > Note > > Synced tables observe the same restrictions as [share links](/docs/protecting-share-links-on-a-base), including password and domain restrictions. | Action | Owner/Creator | Editor | Commenter | Read-Only | | --- | --- | --- | --- | --- | | Set a password on a syncable view share link | ✅ | ✅ | | | | Provide a required password when creating a synced table | ✅ | ✅ | | | | Set an email domain restriction on a syncable view share link | ✅ | ✅ | | | | Create a synced table when a domain restriction is in place (creator's email must match the restriction) | ✅ | ✅ | | | | Reconfigure a broken sync after restrictions are added or changed | ✅ | | | | | Regenerate a syncable view share link URL | ✅ | ✅ | | | | Re-enable sync after a share link URL is regenerated or sync is disabled | ✅ | | | | --- ## Two-way sync permissions > [!CAUTION] > Note > > - Individual field permissions set in a source table are not transferred to the destination. To restrict access to specific fields in a destination, either select the fields in the sync source configuration or request that the destination base Owners apply field permissions. > - Exception: When a field in the source cannot be edited, the field will also be uneditable in any destination. > - The ability to edits two-way syncs is determined by the following settings: > - Sync source configuration > - Sync destination configuration > - Individual field or table editing permissions applied to either | Source permissions | Destination permissions | Owner/Creator | Editor | Commenter | Read-Only | | --- | --- | --- | --- | --- | --- | | Two-way editable (All editable fields) | Not restricted (Editors and above) | ✅ | ✅ | | | | Two-way editable (All editable fields) | Semi-restricted (Creators and above) | ✅ | | | | | Two-way editable (All editable fields) | Fully restricted (No one allowed) | | | | | | Two-way editable (Only certain fields)* | Not restricted (Editors and above) | ✅ | ✅ | | | | Two-way editable (Only certain fields)* | Semi-restricted (Creators and above) | ✅ | | | | | Two-way editable (Only certain fields)* | Fully restricted (No one allowed) | | | | | | Not two-way editable | N/A | | | | | > [!CAUTION] > Note > > - *Only the fields made editable in the sync source configuration are editable in the destination. Destination permissions determine who can edit fields. > - When the destination is set to "Fully restricted," the sync functions as a one-way sync regardless of source settings. Owners and Creators can update the destination sync settings to re-enable two-way editing. ### Two-way sync actions by permission level | Action | Owner/Creator | Editor | Commenter | Read-Only | | --- | --- | --- | --- | --- | | Enable "Allow edits from other bases" in sync source configuration | ✅ | | | | | Select specific editable fields in sync source configuration | ✅ | | | | | Set destination sync permissions (not restricted / semi-restricted / fully restricted) | ✅ | | | | | Edit synced records in the destination (when source and destination settings permit; Editors and above) | ✅ | ✅ | | | | Edit synced records in the destination (when destination is set to Creators and above only) | ✅ | | | | | Create or delete records in a synced table (based on base-level permissions) | ✅ | ✅ | | | --- ## Sync configuration permissions > [!CAUTION] > Note > > - End users can only choose shared views in bases where they have Editor or higher permissions when creating synced tables. Collaborators with Commenter or Read-only permissions in a source base may not see all syncable shared views in their organization's Airtable ecosystem. > - This restriction prevents users without edit access to the source base from using a sync as a way to edit source data. > - Example: If a Read-only collaborator selects a sync source that allows edits from destination bases, edits made in the target base would propagate back to the source. > - Read-only collaborators who are given a share link by an Editor or higher-level permission can create syncs, but the additional step serves as a safeguard. Existing syncs are not affected by this restriction. | Action | Owner/Creator | Editor | Commenter | Read-Only | | --- | --- | --- | --- | --- | | Choose a syncable shared view when creating a synced table (without a share link) | ✅ | ✅ | | | | Create a synced table using an explicitly provided share link | ✅ | ✅ | ✅ | ✅ | | View and use existing synced tables | ✅ | ✅ | ✅ | ✅ | ## FAQs **What happens after adding or changing an active share link’s password?** Once you add or change the password of an active share link, all synced tables that source from that view stop syncing until they are reconfigured with the new password. **What happens after adding or changing a domain restriction connected to an active share link?** Once you add or change a domain restriction on an active share link, syncs for users whose email domain no longer matches the restriction will break until updated. **What happens after a source Creator with the required domain is removed from the destination base?** Once a source Creator with the required domain is removed, the sync stops. And another Creator on the destination base with a matching email domain must reconfigure the sync. **What happens after a syncable view share link URL is regenerated?** Once a syncable view share link URL is regenerated, all synced tables that source from that view stop syncing. Reconfigure the sync in the destination base to resume. **What happens after a sync is disabled on the view share link?** Once a sync is disabled on the view share link, all synced tables that source from that view stop syncing. Reconfigure the sync in the destination base to resume.