diff --git a/examples/nextjs-yjs-tiptap/README.md b/examples/nextjs-yjs-tiptap/README.md
index 0eaccfd1022..7c089abc95f 100644
--- a/examples/nextjs-yjs-tiptap/README.md
+++ b/examples/nextjs-yjs-tiptap/README.md
@@ -10,9 +10,6 @@
# Collaborative Rich Text Editor (Tiptap)
-
- 
-
diff --git a/guides/guides.json b/guides/guides.json
index c7580046415..fa37bb26011 100644
--- a/guides/guides.json
+++ b/guides/guides.json
@@ -511,5 +511,19 @@
"topics": ["presence", "tutorials", "data-fetching"],
"technologies": ["react-ui", "react"],
"date": "2026-03-04"
+ },
+ {
+ "title": "How to use public and private threads",
+ "path": "/how-to-use-public-and-private-threads",
+ "topics": ["comments", "authentication"],
+ "technologies": ["react", "nodejs"],
+ "date": "2026-06-23"
+ },
+ {
+ "title": "How to add private commenting to your app",
+ "path": "/how-to-add-private-commenting-to-your-app",
+ "topics": ["comments", "authentication"],
+ "technologies": ["react", "nextjs"],
+ "date": "2026-06-24"
}
]
diff --git a/guides/pages/how-to-add-private-commenting-to-your-app.mdx b/guides/pages/how-to-add-private-commenting-to-your-app.mdx
new file mode 100644
index 00000000000..d97e95b3783
--- /dev/null
+++ b/guides/pages/how-to-add-private-commenting-to-your-app.mdx
@@ -0,0 +1,195 @@
+---
+meta:
+ title: "How to add private commenting to your app"
+ description:
+ "Learn how to add private comments for admins and team members, alongside
+ your normal public comments."
+---
+
+Some apps have comments that only certain people should see—internal notes,
+moderation discussions, or team-only annotations. With Liveblocks Comments you
+can add these alongside your normal public comments, for example with a separate
+“Leave note” button next to the regular comment button.
+
+
+
+Private threads are only available on Team and Enterprise plans.
+
+
+
+## What we’re building
+
+This guide shows how to give two different thread permissions to two different
+groups of users, **admins** and **regular users**. Admins will be able to view
+both public and private threads, whereas regular users will only be able to view
+public threads.
+
+
+
+This guide focuses on building a private commenting UI. For the complete
+visibility and permissions reference, see
+[How to use public and private threads](/docs/guides/how-to-use-public-and-private-threads)
+and [Permissions](/docs/authentication/permissions).
+
+
+
+## How private threads work
+
+A thread’s _visibility_ is set when it’s created, and every comment inside it
+shares the same visibility. Thread visibility is public by default, but a
+private thread can be created by passing the `visibility="private"` option.
+Liveblocks then only delivers private threads to users who have permission to
+read them.
+
+There are three pieces to building this:
+
+1. [Authenticate users](/docs/authentication), and give admins and regular users
+ different room permissions.
+2. Create private threads with
+ [`Composer`](/docs/api-reference/liveblocks-react-ui#Creating-private-threads)
+ or [`useCreateThread`](/docs/api-reference/liveblocks-react#useCreateThread).
+3. Render threads differently depending on their `visibility` property.
+
+## Authenticate users
+
+Before we get started, we need to decide on
+[permissions](/docs/authentication/permissions) for each group. Admin users will
+have full access to all threads, whereas regular users will only be able to see
+public threads.
+
+
+ 
+ 
+ 
+
+
+## Getting started
+
+Run the following command to try this example locally:
+
+```bash
+npx create-liveblocks-app@latest --example nextjs-comments-private --api-key
+```
+
+This will download the example and ask permission to open your browser, enabling
+you to automatically get your API key from your
+[liveblocks.io](https://liveblocks.io) account.
+
+### Manual setup
+
+
+