Notion as a client portal: where it works and when to switch

Notion works as a client portal for one or two small projects, and it stops working well when you need file versions, recorded approvals, contracts and invoices on every job. A good rule: if two or more of those needs are real for you, keep Notion for your own notes and move client-facing work to a tool built for it.

What the Notion-as-portal setup looks like

The usual setup is a Clients database with one page per project. Each page holds embedded links to Figma, Loom or Drive, a checkbox for approvals, a pasted payment link and a shared URL you send to the client.

It spread because it is free to try and flexible. You can build it in an evening, and the pages look clean. For a solo business with one to three active clients, it often does the job.

Notion also keeps adding to the product. Notion 3.0 rebuilt Notion AI as agents that can handle multi-step work, and it added page-level control over who sees each database row. According to the release notes, row permissions are on the Business and Enterprise plans, and they let you share selected rows with consultants or clients while restricting the rest. The introduction to Notion 3.0 frames it as a step toward AI that does work for you, and later updates kept going: 3.1 arrived in November 2025 and 3.2 added mobile AI in January 2026. That makes the pattern more tempting. It does not change what Notion is: a workspace for content, not a system for client work.

Where Notion is genuinely good

Notion is hard to beat as the place where you think. Briefs, meeting notes, voice samples, brand guidelines and a knowledge base all live well in its editor.

It is also fine for a light client page: one project, a video, two PDFs and a note asking the client to confirm they have reviewed it. Set the page to share with the link and send it.

Personal operations work too. A pipeline view, a content calendar, an hours tracker and a money-in, money-out table are all easy to build with a few databases and formulas. Many people keep running their internal operations in Notion long after they move client-facing work elsewhere, and that is the right split.

Where it strains with real clients

None of these problems is a flaw in Notion. They are jobs it was not designed to do, and they compound once you pass a handful of active clients.

Files are limited and unversioned

Notion's help page on uploads says that on the Free plan every file must be under 5 MB. Paid plans allow bigger files, but the page gives mixed figures for different file types, so check your plan before you promise a client a delivery. Beyond limits, there is no real version history for a deliverable. A new upload sits beside or replaces the old one, and "go back to version three" becomes a hunt through a folder.

Payments are a pasted link

Pasting a payment link works, but Notion does not know whether it was paid. There are no automatic reminders, no sequential invoice numbers and no export for your accountant. At twenty or more invoices a year, that becomes real work.

Contracts live somewhere else

You can paste an e-signature link, but then the contract is in a different tool that the client has to learn, away from the deliverable. That means three tools for every project.

An approval is a checkbox

A ticked box is not an approval record. Six weeks later, when a client says "I never approved that," you have a tick and no name, time or version. A proper approval records who approved which file and when.

Client access needs accounts

This is the one that catches people. According to Notion's sharing and permissions page, guests outside your workspace need their own Notion account to access a shared page, and visitors to a link-shared page must be logged in to comment or edit. Public viewing is possible, but the moment a client wants to comment or react, you are asking them to make an account. Some will not.

Permissions are easy to get wrong

The same page explains that subpages take on the permissions of their parent. If you keep several clients inside one workspace and share a parent page by mistake, one client can end up seeing another client's pages. You can set it up safely, but the safe setup takes care and checking, and nothing stops a rushed afternoon from undoing it.

Finding files is slow

Notion search is good for text. For a file you sent to one client three months ago, you search by memory. A per-project file area with versions answers that in two clicks.

What a client actually experiences

It helps to look at this from the other side of the link. A client opens your Notion page on their phone. The page loads, they scroll past the brief, and they find a video link and a checkbox. They are not sure whether ticking it sends you anything. They do not know where the invoice is. If they want to ask a question, they either email you or sign up for Notion.

None of that is a disaster for a small project. But clients judge a business by how organized the experience feels, and a page that feels like your personal workspace tells them you are improvising. A branded portal with a clear list of what is waiting on them, what you delivered and what they owe tells them you have done this before.

There is also the matter of what happens when you are away. If a client needs a file while you are travelling, a portal with their versions already in it lets them help themselves. A Notion page with a link to a Drive folder makes them wait for you to reply.

When to switch

Count how many of these are true for you:

• You have five or more active client projects at once.
• You regularly deliver files over 50 MB, such as video, design source files or large PDFs.
• You send more than twenty invoices a year.
• A client has disputed an approval in the last twelve months.
• You want a signed contract on every project.
• You spend more than half an hour a week keeping the Notion setup working.

If two or more apply, the workaround costs you more than a proper tool would. If none do, stay where you are. There is no prize for switching early.

Our comparison of a client portal against a shared drive covers the same decision for Drive and Dropbox users, and Notion against HoneyBook goes tool by tool.

Keep Notion, move the client-facing parts

You do not need to leave Notion. Keep the internal documents, planning, dashboards and knowledge base there. Move four things out: file delivery, approvals, contracts and invoices.

That split gives you Notion's strengths where they count and a tool with real state where a client needs a record. It also reduces the chance of the problem we cover in why clients ghost your feedback requests: a request buried in a Notion page with no clear next step is easy to ignore.

How Delivvo covers the parts Notion leaves open

Delivvo takes the four client-facing jobs and puts them behind one link, while Notion stays your private workspace.

Here is the flow:

1. A client fills in your inquiry form, and the lead lands on the lead board.
2. You send a quote from packages and add-ons. The client signs a contract with a typed or drawn signature, and the signing record stores a SHA-256 hash, IP address and device with an archived PDF.
3. The deposit invoice and payment schedule are created from the accepted quote. Invoice numbers are sequential in the format you pick.
4. You upload deliverables to the client portal. Each file has versions, and the client approves a specific file with a recorded name and time.
5. The client reaches all of it with no password, using a one-time code, so there is no account to create.
6. They pay through your own gateway, and Delivvo takes 0% of the payment.

Two details are different from a Notion page. First, every invoice, contract and quote carries a verification code that anyone can check on the verify page. Second, the files are real file transfer: your uploads go up to 50 GB on Pro and above, and your client can send files back up to 5 GB each.

Nothing about the move stops you using Notion for the briefs and notes that feed the work. The Free plan has no card requirement, with three clients and 2 GB, so you can run one real client through it before deciding. Solo is $12 a month and Pro is $29. Read more about the client portal and client approvals.

Delivvo is a CRM and client portal for service businesses. See how Delivvo compares with Notion.

FAQ