Share a read-only, branded status link so a client can follow a project without an account, showing only what you choose to publish
Give a client a private link to a live project status page.
The client portal is a read-only status page you can share with a client through a private link. They open it in a browser with no account and no sign-in, and it shows your organization's branding, so it reads as your window onto the project rather than a generic page. The link is the only credential, and it is a long, unguessable secret.
Mint a share link, optionally give it an expiry, and revoke it anytime.
From the project, create a client share link. You can optionally set an expiry date so the link stops working on its own after a point. Creating a link is an edit-level action on the project.
Copy the link and share it however you normally reach the client. Anyone with the link can view the status page; there is nothing else to set up on their side.
Revoke a link at any time to turn it off immediately. A revoked or expired link stops showing the project and reveals nothing about it.
A deliberately narrow, client-appropriate view of the project.
The status page is limited on purpose. It shows only:
It never shows internal-only information: no health rating, no budget or burn, no logged hours, no internal descriptions or notes, no author names, and no deal or pipeline detail. The page shows nothing beyond your branding and the fields above.
You decide, per update, what the client gets to read.
Status updates you post on the project are internal by default. When you want a particular update to reach the client, mark it as client-visible and it appears on the shared status page. Anything you leave internal never shows there. This gives you a clean split: candid internal notes on the project, and a curated public thread the client reads on their link.