How to Set Notion Database Default View per Member Permission Level

Notion database views let each team member see the same data in a layout that suits their role. A project manager may need a Kanban board while a developer prefers a table filtered by assigned tasks. By default, a database opens to the view you last used, which may not match what other permission levels should see. This article explains how to set a default view for each member permission level using Notion’s view locking and sharing features.

How Notion Database Views and Permission Levels Work Together

A Notion database can display the same set of records in multiple views: table, board, calendar, gallery, list, or timeline. Each view can have its own filters, sorts, and property visibility. When a member opens a database, Notion shows the last view that member used, unless a view is locked as the default.

Permission levels control what a member can do with the database. There are three built-in levels: Can edit, Can comment, and Can view. The permission level is set on the database page itself, not on individual views. To show a different default view to editors versus viewers, you must combine view locking with page-level permissions and duplicate the database if needed.

The key limitation is that a single database page can have only one locked default view. If you need different default views for different permission levels, you must create separate linked databases or duplicate the database and restrict access per page.

Steps to Set a Locked Default View for a Specific Permission Level

This method sets one view as the default for all members who open the database. It works when all members share the same permission level on that page.

1. Open the database and switch to the desired view
   Click on the view tab at the top of the database. Select the view you want to be the default. For example, click the Board view if you want project managers to see a Kanban layout.
2. Click the view name dropdown arrow
   Next to the view tab name, click the small down arrow. A menu opens with options for that specific view.
3. Select Lock as default view
   From the dropdown menu, choose Lock as default view. A lock icon appears on the view tab. All members who open this database will now see this view first.
4. Set the permission level on the database page
   Click Share in the top right corner of the page. Under Invite, add members or groups. Set their permission to Can edit, Can comment, or Can view. Members with Can view cannot change the view at all. Members with Can edit can switch to other views but the locked default remains the starting view.
5. Test the default view
   Open the database in an incognito browser window or ask a colleague to open it. Confirm that the locked view appears first.

Using a Linked Database to Show Different Default Views per Permission Level

If you need editors to see a Table view and viewers to see a Calendar view, you cannot do this on a single database page. Instead, create a linked database on a separate page and set a different locked default view there.

1. Create the main database
   Build your source database with all views you need. Lock one view as the default for the highest permission level, such as Can edit.
2. Create a new page for the second permission level
   Click + New page in the sidebar. Name it something like “Read-Only Project View”.
3. Add a linked database to the new page
   Type /linked view of database and select the source database. A linked database appears with all the same data.
4. Switch to the desired view and lock it
   Click the view tab you want viewers to see, such as Calendar. Click the view dropdown and select Lock as default view.
5. Set page permissions for the new page
   Click Share on the new page. Add the viewer group and set permission to Can view. Remove any editor groups from this page so they do not see this linked database.
6. Share the correct page link with each group
   Copy the URL of the main database page for editors. Copy the URL of the linked database page for viewers. Each group sees only their designated default view.

Common Mistakes When Setting Default Views by Permission Level

Locked default view does not apply to all members

A locked default view applies to every member who opens that specific database page. If you want different views for different permission levels, you must use separate pages with linked databases. A single locked view cannot change based on who is looking at it.

Can view members can still switch views

Members with Can view permission on a database page cannot edit data but can still click other view tabs. To prevent view switching entirely, set the page permission to Can view and then lock the view. Even then, a user can click another view tab and see that view. The only way to block switching is to duplicate the database and give Can view access to a page that contains only one view.

Linked database shows all views from the source

When you create a linked database, it inherits all views from the source database. If you do not want viewers to see certain views, you must delete those view tabs from the linked database page. Deleting a view from a linked database does not remove it from the source.

Default view resets after a member changes it

If a member with Can edit permission switches to a different view, that view becomes their personal default. The locked default view only applies to members who have never opened the database or who clear their browser cache. To enforce the default view every time, set the database page to Can view for those members.

Default View Methods Compared: Single Page vs Linked Database

Item	Single Page with Locked View	Linked Database on Separate Page
Number of default views	One default view for all members	One default view per linked page
Permission levels supported	All levels on one page	Different levels per page
View switching allowed	Yes, unless page is set to Can view	Yes, but separate page limits access
Data syncing	Same database, same data	Same source data, synced automatically
Setup complexity	Low, one page only	Medium, requires duplicate pages

Use the single page method when all members should see the same default view. Use the linked database method when editors and viewers need different starting views. The linked database method requires managing multiple page links and permissions but gives you full control over what each permission level sees first.

You can now set a locked default view on any Notion database and control which permission level sees which view. For teams that need editors on a Table view and viewers on a Calendar view, use linked databases on separate pages with distinct permission settings. As an advanced tip, combine the Lock as default view option with page-level Can view permission to create a read-only dashboard that always opens to a specific view for external stakeholders.