Gave every client a private Notion portal with only their own tasks, without duplicating a single database, for a solo business consultant

Client snapshot

A consultant working alone with nine small business clients at a time. Notion held everything in four databases that linked to each other: Projects, Tasks, Meeting Notes and Project Phases. She had moved to the Business plan to give each client a private view of their own tasks.

The problem

The first portal worked for a week and then stopped: one client saw an empty page, another could open tasks that belonged to someone else. She had also tried copying the Tasks database for each client, which meant updating the same task in two places. Every Friday she still wrote nine status emails, because the portals could not be trusted.

What we built

Two Zoom sessions and some work in between.

1. Find what broke. The portal page showed a linked view of Tasks, but the client had only been invited to the portal page, not to the Tasks database behind it. When the workspace moved its pages into a teamspace during the plan change, the old sharing was reset. A linked view can only show what the viewer already has access to.
2. One Tasks database, not nine. The copies were merged back into one Tasks database. Each task already related to a Project, and each Project now has a Client contact field holding the client's Notion guest account.
3. Access by person, not by page. Instead of sharing the whole Tasks database, a permission rule gives each guest access only to the pages where they are the client contact. They see their tasks and nothing else, and new tasks appear for them automatically.
4. A portal page per client. Each client has one page with a filtered view of their open tasks by phase, their meeting notes and a "waiting on you" list. A template makes a new portal in about five minutes.
5. Plain-English handover. A one-page guide covers how the four databases connect, why a linked view needs access to its source, and the three settings to check if a client says their page is empty.

Results, one month in

• Clients who see only their own tasks: none → all nine, checked by logging in as a test guest.
• Friday status emails: around nine a week → none. Clients check their portal instead.
• Setting up a new client: about an hour of copying → around five minutes from the template.

Quote

"I finally understand why it broke, so I can fix it myself next time." Consultant

Build snapshot

• Timeline: 1 week, about 5 hours
• Stack: Notion, Notion Business plan
• Investment: $200
• Who owned it: the consultant adds new clients from the portal template and checks the guest list once a month.

The pattern

Most broken Notion portals are an access problem, not a view problem: a linked view only shows what the viewer can already open. Keep one database, give guests access by person instead of copying data, and test as a guest before sending the link.

---

This is an illustrative composite drawn from operator engagements. Names, identifying details, and exact metrics are anonymised. The workflow, stack, and approach are real.