A client portal tied to the same records.

Clients see the real record, not a status report you rebuilt on Friday.

Try for freeSee pricing

What can you do with the client portal?

  1. Share per account, and tune what each portal member can see and do.

  2. Retainer balance and usage visible to the client, drawn from approved time.

  3. Comments with a clear line between internal and client visible.

  4. Field level indicators so nobody has to guess what the client can see.

What does the client actually see?

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.

Real records, not reports

No Friday status deck rebuilt by hand.

Per-member tuning

Each portal member sees their slice.

Visibility indicators

Nobody guesses what the client can see.

Does sharing mean losing control?

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.

Across the workspace

Know how every client is doing.

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.

What this removes

Account health as an opinion. Nobody has to assemble a history before a renewal conversation.

Can clients see the money?

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.

Where do client conversations land?

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.

Inside the client portal.

Works with

  • Claude
  • Slack
  • GitHub
  • Zoom
  • Gmail
  • Microsoft Outlook
  • Google Calendar
  • Forms

Explore integrations

Switching from another tool?

  • Asana
  • Monday.com
  • Trello
  • ClickUp
  • HubSpot
  • Harvest
  • Notion
  • Confluence
  • Google Sheets
  • Excel

If it exports a CSV or a document, it moves. See how to migrate

Questions people actually ask.

Don't see your question? Contact us

Is the portal per client?

Yes. Each client gets their own portal, enabled deliberately, with its own selection of shared modules and records.

Can different people at the client see different things?

Yes. Portal members carry per-person capability overrides, so a CFO and a day-to-day coordinator get different screens.

Can clients submit requests through the portal?

Yes. Requests land as tickets on your side, with routing and SLA clocks, and the client can follow progress without emailing for updates.

Are shared documents copies?

No. The portal shows the same versioned file you work from, so the client never reviews a version that drifted a week ago.

How do we know what a client can see?

Field-level indicators mark client-visible content across the workspace, and every comment states its visibility before you post it.