How to Set Notion Page Sharing Permission for Specific Comment Threads

You want to share a Notion page with a collaborator but only allow them to view and comment on specific threads, not the entire page content. Notion does not offer native per-comment-thread sharing permissions; all page-level sharing controls apply to the whole page. This article explains the workarounds you can use to limit a guest or team member to only see and participate in selected comment threads.

Why Notion Does Not Support Per-Comment-Thread Permissions

Notion’s sharing model works at the page level. When you share a page, you grant the invited person access to the entire page — its blocks, databases, media, and all comments. There is no setting to restrict a guest to a single comment thread while hiding the rest of the page. This design is intentional: comments are inline annotations attached to specific blocks, and hiding those blocks would break the context of the discussion. If you need to let an external reviewer comment on only one section, you must either duplicate the page or restructure your workspace.

Steps to Restrict a Collaborator to Specific Comment Threads

Because direct per-thread permissions do not exist, the following methods are the closest alternatives. Choose the one that best fits your workflow.

Method 1: Duplicate the Page and Keep Only Relevant Comments

1. Open the original page
   Navigate to the page that contains the comment threads you want to share.
2. Duplicate the page
   Click the three-dot menu at the top right of the page and select Duplicate. A copy of the entire page appears in the same location.
3. Delete blocks unrelated to the target thread
   In the duplicate, remove all blocks, databases, and media that are not part of the comment discussion. Keep only the block or section where the relevant thread is attached.
4. Share the duplicate page
   Click Share in the top right, add the collaborator’s email, and set the permission to Can comment. The collaborator will see only the blocks you retained and can comment on them.
5. Communicate the limitation
   Tell the collaborator that they are viewing a copy and that their comments will not appear in the original page.

Method 2: Use a Linked Database View Filtered by Comment Content

This method works only if your comment threads are inside a database page property or a comment block that contains text you can filter on. It requires creating a new database view that shows only rows with specific comment content.

1. Add a formula property to capture comment text
   If your comments are in a text property, you can use a formula to extract keywords. This step is advanced and may not work for inline comments attached to blocks.
2. Create a filtered view
   In the database, add a new view. Set a filter condition that matches the comment content you want to expose, for example, “Comment contains ‘budget’.”
3. Share the filtered view link
   Copy the link to the filtered view and share it with the collaborator. They will see only the rows that match the filter. However, they can still change the view or see other views if you give them page-level access.
4. Lock the view if needed
   To prevent the collaborator from switching views, lock the database by clicking the three-dot menu on the database and selecting Lock. This restricts view changes but still exposes all rows if the user removes the filter.

Method 3: Create a Sub-Page for the Comment Thread

1. Extract the thread into a separate page
   Copy the block that contains the comment thread into a new page. Include any necessary context blocks.
2. Share the sub-page
   Click Share on the new sub-page and add the collaborator with Can comment permission. The original page remains hidden from them.
3. Link the sub-page from the original
   Insert a link to the sub-page in the original page so that team members can navigate to it. The collaborator will not see the original page unless you share it.

Common Issues and Limitations

Collaborator Sees the Entire Original Page After Being Added

If you add a guest to a page, they see everything on that page. The only way to prevent this is to use a duplicate or sub-page. Double-check that you have not accidentally shared the original page with the collaborator.

Comments in Duplicates Do Not Sync with the Original

When you duplicate a page, comments are copied as static text. New comments added to the duplicate do not appear in the original, and vice versa. You must manually transfer feedback if needed.

Guests Can Still See Page History and Backlinks

Even with Can comment permission, a guest can view the page history and see backlinks. If your original page contains sensitive information, a duplicate is safer.

Notion Sharing Permissions: Page-Level vs Thread-Level

Item	Page-Level Sharing	Thread-Level Sharing (Desired)
Granularity	Entire page	Single comment thread
Permission options	Full access, Can edit, Can comment, Can view	Not available
Workaround required	None	Duplicate page, sub-page, or filtered view
Sync between copies	N/A	No automatic sync
Exposes page history	Yes	Yes, if using sub-page; no if using duplicate

Notion’s current architecture treats comments as part of the block content, not as separate objects with independent permissions. Until Notion introduces thread-level sharing, the duplicate-page method remains the most reliable way to isolate a comment thread for an external collaborator. For internal teams, consider using a dedicated page for each discussion topic and sharing only that page.