Giving clients access without the chaos

If you run client work, you've probably tried one of two approaches to keeping clients in the loop: a separate tool just for them (a shared doc, an email thread), or inviting them straight into your main project tool as a regular member. Both have the same failure mode — either the client is disconnected from where the real work happens, or they end up seeing more of your internal business than they should: other clients' projects, budgets, internal discussions.

A role built for this

Toadflow has three roles: Admin, Member, and Client. Admin and Member cover your internal team. Client is for the people you're doing the work for.

The difference isn't just a label. A Client:

• only sees the projects they've explicitly been added to as a project member — every other project in the workspace, including its board, budget and discussions, is invisible to them
• can participate fully inside the projects they do have access to: view the board, read and reply to the message board, see files
• never sees a workspace-wide view like the Budget overview, which stays Admin-only

Because access is granted per project rather than per workspace, one workspace can comfortably hold several clients' work side by side — each client only ever sees their own slice of it.

Why this matters for pricing too

Because clients are just another kind of member, not a separate paid seat, adding a client to a project doesn't add to your bill. Toadflow's plans are priced per workspace, not per person — so bringing more clients into the loop is free to do, and safe by default.