Portal shares
Turn a portal on per client and choose the modules and records inside it. Nothing is shared by accident.
Clients see the real record, not a status report you rebuilt on Friday.
Every piece that makes this work, and what each one is actually for.
Turn a portal on per client and choose the modules and records inside it. Nothing is shared by accident.
Per person capability overrides, so a client CFO and a client coordinator do not get the same screen.
The same versioned file you work from, not a copy that drifts a week later.
Issued invoices, payment status, and retainer usage, visible without an email chase.
Knowledge articles published into the portal per client, so the help a client sees is the help that applies to them.
Conversation in the portal that lands on the internal record, with visibility on every comment.
Clients told when something they care about moves, without adding them to your internal noise.
Contacts belong to more than one account, which is how agency relationships actually work. Calls, email, tickets, meetings, threads, and events all roll up to one account timeline. The health read is derived from that alongside delivery and commercial signal, so it is a calculation with sources rather than a color someone picked in a spreadsheet.
The long version, because this is where the category has real objections.
The real record, scoped. You enable a portal per client and choose what it carries: projects, tasks, retainers, documents, invoices, and threads. Visibility tunes per portal member, so the client CFO and the client coordinator get different screens, and field-level indicators show your own team exactly what is client-visible before they type.
No Friday status deck rebuilt by hand.
Each portal member sees their slice.
Nobody guesses what the client can see.
No. Nothing is shared by accident: portals turn on per client, modules and records opt in one by one, and every comment carries a clear line between internal and client-visible. The default is closed, and opening something is a decision someone made on purpose.
If you want them to. Issued invoices, payment status, and retainer balance with its burn, drawn from approved time, can all be shared into the portal. The where-are-we-on-hours email answers itself, and so does the one about the unpaid invoice.
On the internal record. A thread in the portal is the same thread your team sees on the project, with visibility controlled per comment, so the client conversation and the internal one stay in the same place without becoming the same thing.
Yes. Each client gets their own portal, enabled deliberately, with its own selection of shared modules and records.
Yes. Portal members carry per-person capability overrides, so a CFO and a day-to-day coordinator get different screens.
Yes. Requests land as tickets on your side, with routing and SLA clocks, and the client can follow progress without emailing for updates.
No. The portal shows the same versioned file you work from, so the client never reviews a version that drifted a week ago.
Field-level indicators mark client-visible content across the workspace, and every comment states its visibility before you post it.
Scrambl is one workspace, so the records here are the same records the rest of the platform reads. These pair with it most often.