You want to share a Notion page with someone but limit what they can see or edit in its database rows. Standard page sharing gives guests full view or edit access to all properties on a page. Notion does not offer a built-in property-level permission system like a spreadsheet application does. This article explains how to achieve granular property-level access using database views, linked databases, and guest permissions.
Key Takeaways: Restricting Property Access in Shared Notion Pages
- Create a filtered database view: Hides entire properties from guests by creating a view that includes only the columns you want to share.
- Use a linked database: Shares a separate copy of the database with only the allowed properties, leaving the original database private.
- Guest permissions + page-level sharing: Restricts guests to a single view of a database, preventing them from accessing other views or the full database.
How Notion Page Sharing Works for Database Properties
When you share a Notion page that contains a database, guests see the default view of that database unless you specify otherwise. Notion does not let you assign read or edit permissions to individual properties within a database row. Every guest with Can Edit access can modify any property in the rows they can see. Guests with Can View access can read all properties in the visible rows.
The workaround uses Notion database views. A view is a saved filter that shows only certain properties, rows, or both. You can create a view that hides sensitive columns such as salary, internal notes, or status fields. Then share only that view with the guest. Because the guest never sees the original full database, they cannot access the hidden properties.
This method works for guests who do not need to see the entire database. If the guest must edit some properties but not others, you can give them Can Edit access on the filtered view. They will still be able to edit only the properties shown in that view. However, if they create a new view of the database, they may see all properties. To prevent this, you must limit their permissions further.
Prerequisites for Property-Level Access
You need a Notion workspace with a database that contains multiple properties. You must have Can Edit or Full Access permission on the database. The guest must have a Notion account or be invited as a guest. You cannot apply property-level access to members of your workspace who have full access to the workspace.
Steps to Create a Filtered View for Property-Level Sharing
- Open the database page
Navigate to the page in your Notion workspace that contains the database you want to share. Click on the database to make it active. - Create a new view
Click the view name at the top left of the database (the default is usually “Table View”). Select Add a view from the dropdown. Name the view something descriptive like “Client View – Read Only.” Choose the view type (Table, Board, or List). Click Create. - Hide sensitive properties
In the new view, click the Properties button at the top right of the database. A list of all properties appears. Toggle off every property that you do not want the guest to see. Only the toggled-on properties will appear in this view. - Filter rows if needed
Click the Filter button at the top of the database. Add a filter to show only specific rows. For example, you can filter by a “Client Name” property to show only rows relevant to that guest. This step is optional but recommended for security. - Share the view with the guest
Click Share at the top right of the page. Under Invite, enter the guest email address. Set the permission to Can View or Can Edit. Click Invite. The guest will see only the filtered view, not the full database.
Steps to Use a Linked Database for Full Isolation
- Create a new page for the linked database
In your workspace, create a new blank page. Give it a name such as “Shared Data – Guests.” - Add a linked database
Type /linked in the new page and select Linked database. Choose the original database from the list. A copy of the database appears, but it is a live view of the original data. - Hide properties in the linked database view
Click the Properties button in the linked database. Toggle off all properties you want to hide. The linked database shows only the toggled-on properties. - Set view permissions
Click the view name in the linked database. Select Lock view to prevent guests from creating new views. This step is critical because a guest could otherwise create a view that shows all properties. - Share the linked database page
Click Share on the new page. Invite the guest with Can View or Can Edit permission. The guest sees only the filtered linked database and cannot access the original database or its full properties.
Common Issues With Property-Level Access Workarounds
Guest creates a new view and sees all properties
If you give a guest Can Edit access on a view, they can create new views. A new view may show all properties by default. To prevent this, lock the view by clicking the view name and selecting Lock view. Locking disables the ability to add, hide, or reorder properties.
Guest sees the original database in search results
If the guest is a workspace member, they may find the original database via search or navigation. To avoid this, invite the guest as a guest rather than a member. Guests see only pages explicitly shared with them. They cannot search the full workspace.
Linked database shows stale data
A linked database reflects changes in real time. If the guest does not see updated data, they may need to refresh the page. Press F5 or click the browser refresh button. If the issue persists, check that the original database has not been deleted or moved.
Notion View Sharing vs Linked Database Sharing: Key Differences
| Item | Filtered View Sharing | Linked Database Sharing |
|---|---|---|
| Data source | Uses the original database directly | Creates a separate page with a live copy |
| Guest can create new views | Yes (unless view is locked) | Yes (unless view is locked) |
| Guest can access original database | Yes, if they have workspace access | No, unless explicitly shared |
| Setup complexity | Low | Medium |
| Best for | Quick sharing with guests who have limited permissions | Long-term sharing with external collaborators |
You can now configure Notion page sharing to hide specific properties from guests using filtered database views or linked databases. Start by creating a new view and toggling off the properties you want to keep private. Then lock the view to prevent guests from bypassing the restriction. For maximum isolation, use a linked database on a separate page that is not connected to the rest of your workspace. Remember to always test the shared page from a guest account to confirm that hidden properties are not accessible.