![]() ![]() If you would like to make it so that all collaborators with editor permissions and above can edit the view's configuration, you can unlock the view by returning it to collaborative view mode. Unlike editors, however, they will see a blue option that they can use to potentially unlock the view. Similarly, creators and owners who open view configuration menus will be able to see the locked view's configuration settings, but not interact with or change them in any way. They will also see a blue option that they can use to duplicate the current view as a personal view. ![]() field visibility menu, filter menu, etc.) will be able to see the locked view's configuration settings, but not interact with or change them in any way. Once a view has been locked, collaborators will not be able to adjust any of the view configuration settings until the view has been unlocked.Įditors who open any of the view configuration menus (e.g. Once you're ready, click the Lock view button. Whether or not collaborators can make changes to records is determined by their permission levels.īefore locking the view, you can choose to add a message that will appear whenever a collaborator tries to unlock a view you can use this message to give your fellow collaborators more context for why a view has been locked. Please be aware that locking a view is only related to view configuration locked views do not have an effect on any collaborators' abilities to view or make changes to the contents of records. You've created a view for a team or process that many collaborators look at frequently You've made a filtered view that's being used for a view share link or embed, and changing the filtering conditions could inadvertently expose sensitive information You've carefully constructed a view to power an app or a Zapier / Slack integration Here are a few examples of when you might want to lock a view: ![]() It's useful to lock a view when unexpected changes to that view's configuration could potentially disrupt your team's workflow. Locked views allow collaborators with creator or owner permissions to prevent all collaborators from altering a view's configuration (i.e., the customizable settings of a view like filtering conditions, field visibility, field order, row heights, and record coloring ) until it's been explicitly unlocked by another collaborator with creator or owner permissions. Collaborative views are visible to any base collaborator. However, Paid plan workspaces have access to two premium view features that allow for greater control over view configurations in a team context: locked views and personal views. The main collaboration setting for views is the “Collaborative” view type. For that reason, you likely want to rename the view and do any further customization in newly added or duplicated views. As a best practice tip, it's good to have at least one view that doesn't hide fields or filter, group, sort, or color records as a reference of the entire dataset present in that particular table. This default grid view will not have any hidden fields, filtered records, grouped records, record sorting, and/or record coloring applied at first. It closely resembles a spreadsheet as the records and fields are organized into rows and columns, respectively. Even if you're looking at your data through the default "Grid view" that comes with every new table, you're still looking at your data through a view.Īs just mentioned, a grid view is the default view type of an Airtable database. Whenever you're looking at your data in Airtable, you're always looking at your data through a view. This means that if you edit the data in a record while in one view, it will change that data for all views since all views are looking at the same record. The most important thing to understand is that a view is just a different way of looking at the same underlying data. You can create up to 1000 views per table in your base. Each view can have its own unique configurations to hide, sort, and filter records within a table. You can use views to show only specific fields or records by applying configurations to manage the information in that view. Views are specific to each individual table in your base. Web/Browser, Mac app, Windows app, and mobile apps Additionally, can lock or unlock views or delete other collaborators' personal views.Įditors - Can add, delete, or modify viewsĬommentors - Can add, delete, or modify personal views ![]() Owners/Creators - Can add, delete, or modify views. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |