Guide

Client portals in Notion

Share matter-specific pages with clients using Notion's granular sharing. Replaces a client portal product for most solo and small-firm work.

By Raghav R Handa, practising lawyerPublished 27 August 2026Updated 22 September 20266 min read

TL;DR

Each client gets a single Notion page that you share read-only or with comment access.
The page pulls from your Matters database via linked views, filtered to that client.
No separate login system. The client opens a link.

Free downloadLawyerOS — Matters, Clients, Billing & AIGet it

The reality

A real client portal does three things: shows the client what matters they have open, shows the documents you have shared with them, and lets them send a message. Notion does all three with native sharing.

The setup

For each client, create a page in a top-level Clientsspace. On the page, embed a linked view of Matters filtered to that client, a linked view of Documents tagged Shared with client and filtered the same way, and a comment thread. Share the page with the client by email at comment-only level. They get a link, they sign in to Notion (free), and they see exactly what you intended.

What clients see and do not see

They see only the page you shared. They do not see the underlying databases. They do not see other clients. Notion's permissions cascade down, never up. As long as the client's page is the only thing shared with them, the rest of your workspace is invisible.

Common mistakes

Sharing a database directly with a client. They will see everything in it. Always share a page that contains a filtered linked view.
Forgetting to remove access at matter close. Build a closing checklist.

The structure in full

A client portal in Notion is a shared page with a status and a few documents, not a secure client-facing platform. Decide what it must do before you build it.

Property	Type	Why
Matter name	Title	What the client sees
Status	Select	Plain-language stage
Next step	Text	What happens next and who does it
Waiting on	Select	You, Client, Third party
Key dates	Date list	Dates the client needs to know
Shared documents	Links	Only what is meant to be shared

Build it step by step

Decide what the client needs: status, next steps, documents, a message route.
Create a client-facing page per matter, separate from your internal matter page.
Share it with named individuals only; avoid public links.
Write a short plain-language update when something changes.
Review sharing quarterly and remove access at closing.

Views worth creating

View	What it shows
Client view	Status, next step, key dates
Awaiting client	Matters where you are waiting on the client
Sharing audit	Who has access to which pages

Mistakes we see

Sharing the internal matter page.
Public 'anyone with the link' access.
Putting privileged analysis on the shared page.
Leaving access open after closing.

Where Notion stops

Check vendor security terms and your regulator's expectations before sharing client information.
For documents and messages that need a secure, authenticated channel, use a purpose-built portal or secure email.

A free starting structure is in the LawyerOS Starter Kit. Nothing here is legal advice; check your regulator's rules for anything you depend on.

Frequently asked questions

Is a Notion client portal secure?

It depends on how you share, the plan, and what you put on it. Share to named people, avoid sensitive detail and review terms. For high sensitivity use a purpose-built portal.

What should clients see?

A plain-language status, next steps, key dates and documents meant for them. Not your internal analysis.

Do clients need a Notion account?

Depends on how you share. Check current sharing options and choose the most controlled one that works.

Related guides