Blue Client Portal
Your workspace.
Scoped for clients.
A client portal that isn't a separate product. Invite clients into your existing workspace, scope what they see down to the records and fields they should, and let them comment, upload files, and check status alongside your team.
Look at this from a client's seat.
Below is a real Blue workspace. The records, fields, and comments a client sees are exactly what's scoped to them — nothing more.
How a client portal actually works on Blue.
Three things, not thirty. The client signs in, sees what you scope, and collaborates the same way your team does.
Invite, don't onboard
Clients sign in with the email you invited them under. No portal admin to set up, no separate user database to maintain, no second product to bill them for.
Scope what they see
Workspace-, record-, and field-level permissions hide your internal pipeline, margins, and team chat — clients see only what you've explicitly shared.
Real collaboration
Clients comment on the deliverable, @mention your team, upload files, and check status. The same surface your team uses, just scoped down.
01 · What clients see
Same product. Different surface.
Permissions decide what shows up in their view. Comments and @mentions keep the collaboration in the workspace, not in email.
Getting started with our team
Onboarding docs in the workspace.
Welcome guides, project briefs, and SOPs live alongside the records they apply to — clients land in the right context on day one.
Love the v3 designs — one note: can we make the CTA copy stronger?
On it — will push a revision by end of day.
Comments in context.
Clients comment on the deliverable itself. Decisions stay attached to the record they apply to.
@mention to keep things moving.
Loop in your team or theirs without leaving the record. Notifications go to the right person, every time.
02 · Field-level scoping
Decide field by field. Not page by page.
Most "client portal" products give you a single switch — show or hide a page. Blue lets you decide field by field. Show the deliverable status; hide the budget. Show the deadline; hide the assignee. Show what's safe; hide what isn't.
Clients in your workspace. Not a bolted-on portal.
No separate portal product to buy or maintain — clients collaborate in the same workspace as your team, scoped by permissions. Clients count toward your plan like any member, so size your tier to your team plus the clients you bring in.
Starter
For freelancers & small teams
One-time payment
- 5 users
- 5 workspaces
- 2,000 records per workspace
- 5,000 records per org
- 10GB storage
- 250 automations / month
- 3 webhooks
- 3 dashboards
- 1 custom role
- 20 req/s API rate limit
- Community support
Growth
For growing teams
One-time payment
- 30 users
- 25 workspaces
- 2,000 records per workspace
- 25,000 records per org
- 100GB storage
- 1,000 automations / month
- 10 webhooks
- 10 dashboards
- 3 custom roles
- 50 req/s API rate limit
- Email support
Scale
For large organizations
One-time payment
- 150 users
- 100 workspaces
- 2,000 records per workspace
- 100,000 records per org
- 500GB storage
- 5,000 automations / month
- 50 webhooks
- 25 dashboards
- 5 custom roles
- 200 req/s API rate limit
- Email support
One workspace.
Yours and theirs.
Stop maintaining a separate portal. Invite a client into your existing workspace, scope what they see, and run the engagement in one place.