How to Set Notion Database View Lock With Per-User Override Permission

You want to lock a Notion database view so that collaborators cannot change its filter, sort, or layout, but you still need certain team members to be able to edit that same view. Notion’s Lock Database View feature prevents accidental or unwanted changes to a view, but it applies globally to everyone who can access the database. This article explains how to set up a locked database view and then grant an override permission to specific users using Notion’s group permissions and custom views.

How Notion Database View Lock Works and Why You Need a Per-User Override

Notion’s Lock Database View is a toggle available in the view menu (the small arrow next to the view name). When enabled, it prevents all users from changing the view’s filters, sorts, grouping, or column layout. This is useful when you want to present a standardized report or dashboard without team members accidentally rearranging columns.

However, the lock applies globally to everyone who can view the database. There is no built-in per-user override. To achieve per-user override, you must create a separate view of the same database, lock that view, and then use Notion’s page-level permissions to grant edit access to specific users or groups while keeping others as viewers. This approach works because Notion allows multiple views of a single database, and each view can have its own lock setting. The key is controlling who can see and edit the locked view through the parent page’s permissions.

Steps to Set a Locked Database View With Per-User Override

1. Open your database as a full page
   Navigate to the page that contains the database you want to lock. Ensure the database is displayed as a full page (not inline). If it is inline, click the database title and choose “Open as page” from the menu.
2. Create a duplicate view for the override group
   Click the view name at the top left of the database (e.g., “Table View”). Select “Duplicate view” from the dropdown. Name the duplicate something like “Locked View – Editors Only.” This view will be the locked version that only certain users can edit.
3. Apply the lock to the duplicate view
   With the duplicate view selected, click the view name again and choose “Lock Database View” from the dropdown. Confirm the lock in the pop-up. The view is now locked for all users who can access this database.
4. Create a second view for everyone else
   Now create another duplicate of the original view. Name it “General View – Read Only.” Apply the same lock to this view. This view will be the one that all users see by default.
5. Set up group permissions on the database page
   Click the “Share” button in the top-right corner of the page. Add the users or groups that need override permission. For those users, set their permission to “Can edit.” For all other users, set their permission to “Can view” or “Can comment.” This step is critical because only users with edit access to the page can see and edit the locked view.
6. Hide the override view from non-editors
   In the share settings, ensure that the override group has “Can edit” permission. For the general group, set “Can view” and remove their access to the “Locked View – Editors Only” view. To do this, click “Edit” next to the general group’s name, then uncheck the view’s name under “Visible views.” This hides the locked editor view from non-editors.
7. Test the setup
   Log in as a user from the override group. They should see both views and be able to edit the locked view (because they have page edit access). Log in as a regular viewer. They should see only the “General View – Read Only” and cannot edit any view because they have view-only permission on the page.

Common Issues When Setting Per-User Override for Locked Views

Override users see the locked view but cannot edit it

This happens when the override user has “Can view” permission on the database page instead of “Can edit.” Go to the Share menu and change their permission to “Can edit.” Also confirm that the locked view is not set to “Can view” for that user in the view visibility settings.

Non-editors can still see the locked view in the view switcher

If non-editors see the locked view in the dropdown, you did not uncheck the view in their share settings. Edit the share settings for the general group and uncheck the “Locked View – Editors Only” view under “Visible views.”

Changes made by override users are not reflected in the general view

Each view is independent. Edits made in the locked view (e.g., adding a new column) do not automatically appear in the general view. You must manually update the general view’s layout if you want it to match. Alternatively, use a database template that both views inherit from, but that is more complex.

Item	Locked View (Override)	Locked View (General)
Purpose	Allow specific users to edit the view	Show a read-only version to everyone else
Lock status	Locked	Locked
Page permission required	Can edit	Can view
Visible to override group	Yes	Optional (usually hidden)
Visible to general group	No	Yes

This method uses two separate views of the same database. Notion treats each view as an independent configuration. By controlling page-level permissions and view visibility, you effectively create a per-user override for the lock. The override group can edit the locked view because they have edit permission on the page, while everyone else sees a separate locked view that they cannot modify.