Home / Writing

A Notion Client Portal Template Clients Open Twice

Clients do not want your workspace

A client does not open your project page to admire your system. They want four answers in under a minute: what is happening on my project, what do you need from me, where does the invoice stand, and when do we next talk. Most Notion client portal template builds are organized around how the freelancer works rather than what the client came for, and that is the first reason they go unread.

The second reason is volume. A portal with forty linked items looks good in a screenshot and exhausting on a Monday. Clients open the page when something is on their mind: a date, a payment, a decision they owe you. If the answer is below the fold, they send an email asking instead, which is the exact cost the portal was supposed to remove.

A Notion client portal template with four sections

Four sections, in this order:

  1. Where we are. One line of status and a short milestone list with dates. Percentages only if the percentage is real.
  2. What I need from you. A task list filtered to this client, with due dates. It should be visibly empty when nothing is needed.
  3. Invoices. Invoice number, amount, due date, status. Not your private notes about the invoice.
  4. Next call. One date and an agenda of three bullets.

Everything else is optional, and optional is where portals go wrong.

What to show and what to keep internal

ItemShow the clientKeep internal
Milestone datesYes
Deliverable statusYes
Hours loggedOnly on hourly or capped retainersOn fixed-fee work
Your internal rateNoYes
Subcontractor costsNoYes
Project scratch notesNoYes
Invoice number and due dateYes
Your total income for the monthNoYes

The hours row is the one people argue about. On a retainer with a visible cap, hours belong in the portal because the client is paying for them. On fixed-fee work they invite a conversation about price that you did not want to have, so leave them out.

One more rule for this section: name things the way the client does. If their internal name is Phase 2 Migration, the portal should say Phase 2 Migration, not Deep Work March. Recognition is most of the reason they open the page at all.

Build it from shared views, not copies

The portal is one page with linked views of four internal databases: Clients, Projects, Tasks, and Invoices. Each view is filtered on a relation to the client whose portal it is. Share the page, never the database. A duplicated copy breaks the moment you update the original, and a shared database invites someone to click into rows you never meant to expose. If you are building the four databases from scratch, the database guide explains properties versus views before you get to the sharing step, and the relations setup covers the link between clients and projects.

One formula that earns trust

`` dateBetween(prop("Last Updated"), today(), "days") ``

Type it into a Formula property called Days Since Update. Above seven days, the number on the portal starts telling the client the truth about your week. That is uncomfortable, which is why it works: the page stops being a brochure and starts being a status report.

A second formula, if the project has a named blocker owner:

`` if(prop("Blocked By") == "Client", "Waiting on you", "With me") ``

Two words that prevent most of the emails that open with "any news on this?"

The permission rules that matter

Sharing a Notion page is not the same as hiding things on it. Three rules cover most of the risk.

Hiding a property is not access control

Hiding a property in a view is a display setting. If the data lives in a shared database, assume a determined viewer can reach it. Internal notes belong in a separate database that is never shared, not in a hidden column.

Never relate a shared database to a private one

A relation can expose the rows it points at. If your shared project tracker points at a rate card or a cost database, the client may be able to follow that link. The rule is blunt: no relation from anything shared to anything you would not hand over.

Check what a guest seat costs on your plan

Guest billing differs by plan and by workspace size, and inviting every client as a guest adds up. Check your plan's guest terms before you invite the fifth client this quarter. Sharing one page by link is not always the right answer either, so decide per client rather than by default. Notion has changed guest billing more than once, so read the current plan page rather than a blog post.

When a single page beats a live portal

A database-backed portal takes maintenance. A weekly snapshot page takes ten minutes. Which one you need depends on the engagement:

EngagementBetter buildWhy
Fixed-fee project, two monthsOne shared page, updated FridayClient checks weekly, so live views add nothing
Ongoing retainerFiltered live viewsStatus changes faster than a Friday update
Several client stakeholdersLive views, need-from-you list on topSeveral people want the same answer
Client who never opens itOne page plus a weekly emailA portal nobody opens is a hobby

The last row is not a joke. Check whether the client opened the page during the first month. If they reply by email with questions the portal already answers, the portal is in the wrong place, not the wrong shape.

Ask one question when you build it: who opens this page, and what are they looking for on the day they open it. Every item on the page should be an answer to that question, and everything else can wait for the meeting.

Do this today

  1. Create the portal page with the four sections and share it with one client as view-only.
  2. Move every internal note out of the shared databases into a database you never share.
  3. Add the two formulas and put a ten-minute Friday update on the calendar.