Each client gets a portal scoped to their own work. They see what you share. They don't see anything else — not other clients, not your internal chatter, not the rest of your workspace. The visibility check is in the database, not the UI.
Free during beta · Client contacts are not seats · No additional cost per client
The whole point of a client portal is the boundary. Workhouse's is enforced where it counts.
Most “client portals” are a separate view rendered by the application. Hide a column in the UI, drop a flag from a JSON response, call it a day. That works until someone crafts a URL or sniffs an API call.
Workhouse handles visibility one layer down. Every task, comment, and audit event has a visibility column. The portal's database queries include WHERE visibility = 'client' and scope to the client's account. A guessed URL doesn't hit a 403 — it hits a 404, because as far as the portal's data layer is concerned, that row doesn't exist.
You can't leak what you never load.
A working surface for the client, not a static dashboard.
Each client only sees their own engagement. No cross-client leakage by URL or otherwise.
Workspace logo and accent color on every portal. To your client, it reads as your agency, not as Workhouse.
One-click sign-off. The decision lands in the activity feed; your team gets notified.
Assigned action items are emailed to the contact. They can click through and complete the loop from email or from the portal.
Clients send new requests through the portal. Your team triages them like any inbox.
Choose which fields (priority, due date, assignee) clients see by default — and override per task when needed.
Invite as many client contacts as you need. They don't count against your team seat total — not now, not when paid plans launch. Charging per-guest is one of the reasons agencies don't roll out the portals they already have.
Yes. Their comments are always client-visible (they can't post internal-only). Your team replies in the same thread; if your reply is intended only for the team, flag it Internal before sending.
No. Each client's portal is scoped to their own account. They don't see other clients in your workspace, by design and by SQL.
Action items, approval requests, and any task comments addressed to them. Internal-flagged activity never produces a client-facing email.
Yes — every client engagement can run with or without portal access. Some agencies use Workhouse purely for internal coordination on some accounts.
Coming from another tool? See how Workhouse compares to Notion →