Public client page
The shareable, no-login update page for a single project — how to share it, brand it, and protect it.
Every project has a public client page: a clean, shareable timeline of its progress that anyone can open with just a link — no account, no login. It's the simplest way to keep a client in the loop.
Need one link that covers all of a customer's projects, with sign-in and messaging history? That's the client portal. The public page described here is per-project and needs no account.
Sharing the link
Each project's public page lives at its own share link. Copy it and send it however you like — email, chat, a proposal. The page is set to stay out of search-engine results, so it's only found by people you give the link to.
You control whether the page is reachable from the project's Access control section:
- Take public page offline — hides the entire page (updates and Q&A) and makes the link stop working. Nothing is deleted; all data is kept internally and you can publish again at any time.
Your organization or workspace can enforce whether a page must stay online or protected. If a toggle shows "Set by the organization or workspace — cannot be changed here," that choice is locked at a higher level and can't be overridden on the project.
What the client sees
Opening the link shows a single, focused page:
- A header with your logo, the customer's name ("Project for …"), and an Ask a question button.
- A project title card with the timeline.
- The progress timeline — each update as a dated card, newest first. Cards can include formatted text, a Important badge for key milestones, and downloadable attachments.
- A small copy-link icon on each update, so a client can share a direct link to one specific update.
- If the project is finished or paused, a banner explains it: a completed project's timeline becomes read-only.
Progress and Questions & Answers
When a project has questions and answers to show, the client can switch between two tabs at the top of the page:
- Progress — the update timeline.
- Questions & Answers — previously asked questions and their answers.
Asking a question
Anyone viewing the page can use Ask a question (or Ask about this update on a specific card). A short form asks for their name, email, and message, and lets them mark it Normal or Urgent. The form shows who the question will reach — a specific team member or a team — so the client knows their message is going to the right place. Their name and email are remembered in their browser for next time.
If you've turned messaging off for a project, the "Ask a question" options simply don't appear — the page becomes read-only for the client.
Password protection
For sensitive projects, you can require a password before the page loads. Clients then see a lock screen and enter the password you gave them to unlock the timeline.
Open the project and expand the Access control section.
Switch on Password protection.
Enter a password and save it. You can reveal the current password later with the eye icon, or set a new one at any time.
Share the password with your client through a separate channel from the link itself.
Wrong entries show a clear message, and repeated failed attempts are temporarily rate-limited to keep the page safe.
Password protection is a Sennith Pro feature.
Branding & white-label
By default the page carries a light "Powered by Sennith" footer. With Sennith Pro branding, you can make the page feel like your own. In your workspace's branding settings you can set:
- Your logo — replaces the Sennith mark in the header.
- A tagline — a short line shown under the logo.
- Primary and accent colors — applied to headings, links, and highlights across the page.
- A portal label — the small caption in the header (for example "Client Portal").
- Footer text — replaces the default "Powered by Sennith" footer with your own.
Turn branding on with the Enable toggle, then save. Every public page in that workspace picks up the look automatically.
On Team plans, your organization can lock branding so every workspace shares one consistent look. If your branding fields are read-only, they've been set at the organization level.