Stop sending status updates. Give your client the actual work timeline.
Toggle a client on. They sign in, pick a project, and see the curated timeline you would have re-typed into an email anyway. Internal entries stay invisible. Auto-generated weekly reports wait for your approval before they fly out.
Flip "Client view" on. Watch the internal entries vanish.
Filter by project, department or tag. Click "Preview next report" to see exactly what the client would receive on Monday morning — internal notes already stripped out.
Turn on portal access for a client. The portal already has their data.
No second product, no separate database, no re-keying. Flip `portal_enabled` on a client, invite their users, and the portal lights up with the projects, entries and files they were already part of — filtered to what you grant.
- One toggle per client — no separate billing, no second app
- Multiple users per client — each with their own login
- Multi-project view per client, with an "All projects" lens
Mark an entry "internal" and the client never sees it. That is the whole story.
Every timeline entry has a visibility flag. Internal infra refactors, vendor squabbles, half-baked ideas — all hidden by default if you mark them so. The portal renders only the entries you flagged for the client. No accidental leaks, no copy-paste sanitisation pass.
- Per-entry internal flag — hidden everywhere in the portal
- Department + tag filters available to the client too
- Date range filtering, with infinite scroll on long projects
Auto-drafted weekly and monthly reports, gated on your approval.
A scheduled job stitches the week’s portal-visible entries into a clean PDF and parks it in the approval queue. You skim, edit, approve. Logbook emails the PDF to the client and links them back to the live timeline. Decline it and nothing leaves the building.
- PDF + email digest, drafted from the timeline you already wrote
- Manual approval gate — nothing auto-sends without sign-off
- Localised email template, project link back to the live portal
Clients can request work. It lands as a board card with their name on it.
The portal is not read-only. Clients submit requests — from the portal or from connected channels like WhatsApp — and Logbook drops them into a dedicated "Client requests" board list, ready for triage. No more "did anyone see that email?".
- Built-in request form, plus optional WhatsApp channel ingest
- Drops into a dedicated board list, attributed to the requester
- Notification fires to the project team — zero email babysitting
Status updates that the client can actually browse.
- Effort to produceRe-write the week into prose every Friday afternoon.The timeline is already written. Approve the auto-draft.
- What the client getsA wall of text in their inbox — archived in 30 seconds.A live, filterable timeline + an emailed PDF — both kept forever.
- Risk of leaking internal stuffHigh — you are copy-pasting from internal notes.Zero — internal entries cannot reach the portal.
- Two-way requestsReply-all chains, lost in inboxes.Request form + WhatsApp channel, lands as a tracked card.
The status-email tax, gone.
0
status emails to write
The portal is the status update
0
toggle to enable a client
No separate product, no migration
0
channels for client requests
Portal form + WhatsApp ingest — both land as cards
0%
of reports gated on approval
Nothing auto-sends without your sign-off
One portal, many engagement models.
A premium-feeling client experience without building a second product.
Each client gets their own branded portal view of the projects you run for them. They self-serve the timeline, you stop being a status-email machine.
- Per-client branding and project scoping
- Auto weekly digest, manual approval gate
- Request form replaces the dreaded reply-all thread