- Premiers pas avec Airtable
- Automatisations Airtable
- Bases Airtable
- Versions bêta d’Airtable
- Collaboration avec Airtable
- Assistance Airtable Enterprise
- Informations générales
- External badging in Airtable
- Creating and using Airtable components
- Ask an Expert beta overview
- Data residency at Airtable
- Présentation des groupes d’utilisateurs d’Airtable
- API Enterprise Airtable
- Creating and managing data retention policies in Airtable
- eDiscovery APIs in Airtable
- Accéder aux journaux d’audit Enterprise dans Airtable
- Configuration de la connexion de Jira Server/Data Center à Airtable
- Panneau d’administration Enterprise
- Présentation du panneau d’administration Enterprise
- Utilisateurs — Panneau d’administration Enterprise d’Airtable
- Détails sur les utilisateurs - Panneau d’administration Enterprise d’Airtable
- Groupes - Panneau d’administration Enterprise d’Airtable
- Espaces de travail - Panneau d’administration Enterprise d’Airtable
- Bases - Panneau d’administration Enterprise d’Airtable
- Interfaces - Panneau d’administration Enterprise d’Airtable
- Data sets - Airtable admin panel
- Managed apps - Airtable admin panel
- Components - Airtable admin panel
- Paramètres - Panneau d’administration Enterprise d’Airtable
- « Procédure Enterprise »
- Gestion des admins Enterprise depuis le panneau d’administration
- Utilisation des organisations
- Organizational branding for apps in Airtable
- Main template
- Enterprise Hub : Org unit assignment with user groups
- Désactivation et réactivation des utilisateurs Enterprise
- Gestion de l’accès des utilisateurs aux espaces de travail et aux bases
- Main template
- Authentification unique pour Enterprise
- Configuration de l’authentification unique avec Okta
- Configuration d’une authentification unique avec Google
- Configuration de l’authentification unique avec OneLogin
- Configuration de l’authentification unique avec Microsoft Entra ID
- Configuration d’une authentification unique avec ADFS
- Fédération de domaine et vérification Airtable
- Informations générales
- Extensions Airtable
- Champs Airtable
- Intégration avec Airtable
- Interface Designer Airtable
- Formation et ressources
- Gestion avec Airtable
- Politique Airtable
- Entrées Airtable
- Synchronisation Airtable
- Vues Airtable
- Impression
- Partager
- SombreLumière
- PDF
Expanded editing capabilities for synced fields
- Mis à jour le 17 Jul 2024
- 1 Minute à lire
- Impression
- Partager
- SombreLumière
- PDF
What’s changing with two-way sync editability?
Starting in August 2024, Airtable is enhancing its two-way sync functionality by allowing users to edit linked record and user fields within synced tables. If you currently have "All fields editable" selected in your sync source configuration, these fields will become editable.
This update is part of our ongoing efforts to make Airtable's platform more powerful and flexible. By expanding sync capabilities, we're giving you greater control over your data and workflows. However, we understand that this change may affect existing processes, so you may want to review any existing syncs to make sure users at your organization aren’t editing data that they shouldn’t.
What actions do I need to take?
Your required actions depend on your preferences for field editability. By taking these steps, you can maintain your current workflow while still benefiting from the expanded capabilities where desired. We recommend reviewing your sync configurations before the August update to ensure your data remains as accessible or restricted as you intend.
If you're comfortable with this expanded editable within the specific source tables where “All fields editable” is enabled: no action is needed. The new capabilities will be automatically available to you in early August.
If you want to restrict the editability of specific user or linked records fields -> you may want to audit specific tables that will be impacted by this change. To make these edits:
Navigate to existing views that are the source of an outbound sync
Change the setting from "All fields editable" to "Specific fields"
Unselect the user fields or linked record fields you want to keep non-editable