Agencies
Let the client in. Only that far.
Client work has a shape every agency knows: a shared channel that goes stale, a folder of docs nobody can find, and a status email written on a Friday. Fora gives the client a project — the real one your team works in — and that project is the entire extent of what they can reach.
Launch Website
One project: its tasks, docs, meetings and chat. What the client sees is what you're doing.
A project per client, and that's the whole of it
A guest in Fora is not a junior member with things greyed out. They're outside the company, and the server treats them that way — your roster, your reporting lines and your other clients aren't filtered from the response, they're never in it.
- Invite by email; they land as a member of that one project
- No company feed, no other clients, no second workspace to run
- The org chart isn't hidden from them — it isn't sent at all
- They meet only the people who are on the projects they share
How we ship
We ship from main. Every change lands behind a flag and is off for everyone.
Flags flip on Tuesday and Thursday at 10:00 Toronto. Nothing flips on a Friday, and nothing flips during launch week without Marcus.
If it isn't written in Fora, it did not happen: the release note is the source of truth, and it links the task it shipped.
View or edit, decided per person
The access belongs to the person, not to the project — so the client's marketing lead can be editing while their legal reviewer only reads, on the same project, without you maintaining two copies of anything.
- Each guest is set to read or to work, individually
- A read-only client can follow everything and change nothing
- An editing client can comment, close tasks and write in the docs
- A shared link, where you'd rather not invite anyone, is view-only
Hana SatoStandup
Jamal CarterSSO walkthrough deck
Noor RahmanMobile tab barThey can't widen the door you opened
This is the part that decides whether an agency can actually use a shared workspace. A guest may do the work they were invited to do and may not change the terms they were let in on — enforced where it counts, not by hiding a button.
- A guest can work inside a project; they can't change its sharing
- Opening Share and promoting themselves is refused by the server
- An admin console tab lists every guest and what they've been let into
- Workspace policy can turn guest access off entirely
2 action items → tasksThe client sees the work, not a report about the work
The Friday status email exists because the client can't see anything the rest of the week. When they can, the email stops being necessary — and the conversation about a deliverable finally happens next to the deliverable rather than in a thread about it.
- Tasks move on the board they're already looking at
- The brief and the deliverables are docs in the same project
- Meetings keep their agenda, notes and action items
- Approval happens where the thing being approved lives
Launch Website
Questions
Do we need a separate workspace per client?
Can a client see our other clients?
Do guests cost a seat?
What if we don't want any external access?
Can a client join a call?
Keep reading
Run the whole company from one place.
Start freeFree for up to ten people. No card. Bring the company. Leave the stack.