Data sets and verifying data in Airtable

First, navigate to the base, then the table, and lastly, the view that you would like to add to your organization's data library.

Click Share and sync option and then click the Publish to data library option.

Note

For a more in-depth walkthrough of the view share menu consult this article.

By default, the user currently publishing the data set (you) will be assigned as the data set's "owner." However, you can also assign ownership to another user with creator permissions in the base where the data set is being sourced from. 

Note

If you see a greyed-out name of a user you would like to be the owner then it likely means they do not have the appropriate permissions in the base. Consult this article for information on how to add a new base collaborator or change their permissions.

By default, any user with base creator permissions will be able to see and add the data set from your organization's data library. However, by toggling on this option, you can choose particular user groups to share the data set with. This is particularly helpful when there is sensitive data or data only relevant to certain groups that you would like to hide from the larger organization.

Here you can choose whether to lock the view. By default, this option is toggled on. Remember, that records can still be modified in other views in the table where the data is being stored. The main reason for this feature is to prevent accidental changes to the configuration of the view being used as the source of the data set.

On the right portion of the setup screen, you'll see a general preview of how the data set will appear in the data library to other users. Once you have determined that the data set configuration is complete click Publish. After publishing, the data set will appear in your organization member's data library and can be verified by an admin.

Navigate to the base where you would like to add the data set. Remember that this will essentially create a synced table in the base that cannot be edited. However, the data can be viewed and enriched with additional fields in the table that is created.

First, click the + Add or import option to create a new table. You'll find this option next to the furthest right table in the base that is open. Clicking this will open a dropdown menu where you will see a section titled "Add from data library." In this section, you'll see 3 suggested data sets that are popular in your organization as well as the option to view x more data sets >. Clicking that option will open the data library.

If you clicked to view more data sets, then a popup will appear with more choices from your organization's data library. 

Verified data sets that have specifically been marked as trustworthy by your organization's admins will show a Verified badge next to the name of the data set. 

Clicking on any data set will open a preview of the data set containing:

• An interactable embedded preview of the data set

• A description of the data set

• The number of records and fields in the data set

• The number of other bases currently syncing to this data set 

• The owner of the data set

• When the data set was last updated

When you have confirmed that this is the correct data set to use, click Add this data. Depending on the size of the source, it may take a few moments for the source data to sync over. You'll see a new synced table appear in the base when it is finished processing.

• By default, all members of the org can publish a data set. However, admin can control this by the admin setting toggle: Allow only admins to publish data sets within the Data sets panel.

• Only admins can verify a data set to mark it as a verified data set.

• A data set is published from a view. The organizational unit that owns this view (org unit ← workspace ← base ← table ← view) “owns” the data set.

• Data set ownership:

  • Owner of data set is nominal (i.e. to facilitate communication)

  • On nomination, we require the user to be a collaborator of the base the data set belongs to, but we don’t enforce it afterwards.

• Admin Management

  • Super admins can manage all datasets owned by any organizational unit within the hub organization.

  • Org unit admins can manage all datasets owned by the organizational unit that they are an admin of.

• Published data set audience scopes

  • Once published, a data set is only visible to the members of the audience user groups selected

    • If you are a super admin, then you can publish to the entire Enterprise Hub.

    • If you are a member of an org, then you can publish to:

      • An entire org unit the base belongs to.

      • Or to multiple groups with the following options:

        • Groups owned by the current data set’s org unit.

        • Groups owned by the current data set’s org unit’s ancestors. Note that we do not include data set’s org unit’s descendants.

        • Members of the organization

  • Ultimately, this means that, no one, even super admins, can choose sibling/children org units as an audience. This was by design in order to not expose descendant organizational unit’s member information to ancestral members.

Syncing a published data set is affected by the syncability of the underlying shared view. Thus, impacted by the org level sync restrictions controlled by the admin in Admin panel. Learn more about synced view restrictions in this support article.

To sync from a dataset, in addition to the user being part of the published audience scope, the org level sync setting should allow syncing of data across the two bases by being set to “Unrestricted.”

• For example, even if the published scope for the dataset is Enterprise Hub, if the admin sync setting of the org unit the dataset resides in, is “Restricted to org”, the data set can only be synced to bases that belong to the same org unit.

• In order for the data set to be synced to bases external to the org unit (even if it’s in the same hub), the sync setting needs to be unrestricted.

Here’s a helpful table to break down the expected behavior of this setting:

After logging into Airtable on the browser of your choice, visit this link to open your organization's admin panel.

After opening the Admin Panel, click the Data sets option on the left sidebar.

From here you can search for a specific data set by name or scroll through the list of data sets to find it. To filter the list to only show data sets that are not currently verified, set the filter next to the search bar to Published only.

On the right side of the data set you are viewing click the three-dot ... icon to open a menu of additional options. Next, click the option to Verify data set. The screen will refresh after a moment and you should see a check appear in the Verified column next to the data set you just verified. 

Note

If you chose to filter the data sets page to show Published only, then the data set will no longer appear in view because it has been filtered out since it is now verified.

Removing the verification badge from a data set follows similar steps to what is listed in the steps above. The main difference is that the option to Verify data set will now instead appear as No longer verify data set. Additionally, you may want to filter the Data sets page to only show data sets that are currently verified by choosing the Published and verified option in the filter dropdown menu.

After logging into Airtable on the browser of your choice, visit this link to open your organization's admin panel.

After opening the Admin Panel, click the Data sets option on the left sidebar.

Below the toggle to Allow only admins to publish data sets you'll see the option to show Inactive data sets. Click this and move on to the next step.

From here you can search for a specific data set by name or scroll through the list of data sets to find it. You'll see an option, Make active, that when clicked on will take you to the base where the issue is occurring. As a reminder, we list those potential issues at the top of this section. 

Note

Sometimes, when a browser window is below a certain size, the Make active button may appear truncated, as shown in the image above.

Once in the base, you'll see one or more warning messages explaining what will need to be resolved to reactivate the data set.

Any issues will need to be resolved before the data set can be reactivated. Using the example from the last step, let's say that a password was accidentally enabled for the data set. To resolve this, you'll need to:

1. Click the blue back arrow that is highlighted. 

2. This will return you to the main Share and sync settings menu.

3. From here, click Link settings.

4. Then toggle off the Access is password-protected option.

5. This will open a confirmation pop-up. Click Remove password. 

Now that you've resolved the issue or issues that caused the data set to become inactive you can either click back to the Link settings or click the Share and sync button to open the view share settings menu again. From here:

1. Click the Publish to data library option. 

2. This will open the next window. Confirm that All issues have been resolved.

3. Finally, click Make active to reactivate the data set.

Note

In the Admin Panel, you'll need to refresh the Data sets page in order to see the reactivated data set appear back in the list of Active data sets.

• Being an Organization member means that user has been claimed by a single enterprise account. More about Organizations can be found in this support article.

• Users who are not a member of the organization will not see Data set as an option in the data library while adding a new synced table, even if that base is enterprise owned.
  Example: Personal accounts won’t see data sets in the data library. They will see existing synced tables though.

Data sets are ordered in the data library as:

• Verified data sets first, then unverified data sets. 

• Within those two larger grouping orders, data sets will then appear in the order of most recently published to least recently published.

As a workaround to bump a data set to the top of the view order, an admin can:

1. Remove the data set from the data library.
    

2. Then, publish that data set again.

3. Lastly, verify the data set again.

• In data set previews, the view's group settings will appear the same as they do in the source of the original data set.

• However, when a data set is added to another base those group settings may not be respected. 

• In these cases, you may need to "rebuild" the group settings that were used in the original data set. If the data set owner is not you, then we recommend you contact them so that they can help to consult you on how you might recreate those settings.

We have not included any limits at this time. 

• By default, data sets can be published by any Organization member with creator permissions or higher. Admins can choose to allow only admins to publish data sets in the Admin Panel. 

• Only the organization's admin(s) can verify a data set.

Users must be Organization members (i.e. claimed by a single Organization, read more here) to have access to an Organization’s data library. If a user is not an organization member or an admin, they will not see the library while adding a new synced table in a base, even if that base is owned by the Organization.

By default, a data set is published to the entire Organization but publishers can restrict the visibility of a data set to specific user groups in the publishing flow and when editing a published dataset in the library.

Admins can see the list of data sets in the Admin Panel “Data sets” tab and take various actions to manage them (e.g. search, filter, verify, stop verifying, change metadata)

Note

Regarding admins on multiple organizations: Non-member admins can only see published data sets in the Admin Panel and they cannot access the data library from within a base.

Data verification can be performed by Airtable admins. 

Managing and choosing which data sets should be marked as verified is highly dependent upon your organization's individual needs. 

• It’s important for at least one admin to take the lead on this program – they should be responsible for verifying existing datasets and ensuring that they stay up to date. 

• It’s also important that admins feel comfortable with the quality of this data w/o feeling like they have an unreasonable upkeep responsibility. That’s the reason the ability to establish an owner on a data set exists.

Users must enable a link and ensure that the following are disabled:

• Two-way sync

• Password protected

• Email domain access at the view level (org-wide domain sharing restrictions are fine)

If a user has published a data set and then enables one of these settings, the published data set will move into an inactive state and a user or admin must reconfigure sync settings to reactivate it. 

Data sets are stored in the original bases they are published from. You can view all published datasets in the admin panel, including the bases that they have been synced to. 

Yes! This is the recommended approach for data sets that are already used broadly. Publishing to the data library will work retroactively: 

• Publishing a synced view already in use to the data library doesn’t change anything for bases already using it

•  It immediately gives admins more visibility into their data ecosystem as these bases will be listed as using the published dataset in the Admin Panel.

No, existing syncs will not be affected. The feature to publish a dataset to specific groups is only about setting the visibility of the data set in the library, so if a user is already using that sync, it doesn't change anything for them.

Airtable recommends that the owner of a data set is clearly defined within your organization.

We will only track a source and all bases syncing to that source. This means that syncs of syncs (aka a chained sync) will not show up in the admin panel. 

Yes. Published datasets update automatically, just like regular syncs.

The verified data sets come first, followed by published data sets. Within each of those groups, we show data sets published in descending order.

Yes, because this is how Airtable sync works.