How should an agency set up Flux for client work?
Use one workspace for your agency and one board per client. Your team joins the workspace and sees every client board. Each client joins only their own board as a board guest. AI agents connect with API keys that your team members create. Nobody outside your team takes a paid seat.
| Who | How they join | What they see | Billed on Pro and Expert |
|---|---|---|---|
| Your team | Workspace member (owner, admin, member or viewer) | Every board in the workspace | Yes, per member |
| Client who follows progress | Board guest, viewer role | Their own board, read-only | No |
| Client who comments and signs off | Board guest, member role | Their own board | No |
| Freelancer working on one client | Board guest, member role | That one board | No |
| AI agent | API key created by a team member, over the REST API or the Flux MCP server | What the key's creator sees | No |
A board can start blank or from a built-in template such as Client Onboarding. For a client project column layout to set up by hand, see the client project template or the agency workflow template. More on members and roles: workspaces and roles.
How do you invite a client to their board?
Open the client's board settings, choose the Guests tab, enter the client's email and pick a role. Only workspace owners and admins can invite or remove guests. The steps:
- Create the client's board in your agency workspace, named after the client and project, for example "Acme - Website".
- Open the board's settings and choose Guests. The section is called Single-board guests: people outside your workspace who see only this board.
- Enter the client's email and pick a role: Viewer, Member (the default) or Admin. The next section explains which to choose.
- The client accepts the email invitation within 7 days. They sign in, or sign up for free, with the same email address you invited. A different address is refused.
- The board appears under Guest boards in the client's sidebar, and changes made in the app show up for them live.
- When the project ends, remove the guest from the same tab. You can also revoke an invitation that is still pending.
Which role should a client get?
Give clients the viewer role when they only follow progress, and the member role when they need to comment, approve or add requests. Flux has no comment-only role, so a client who can comment can also edit cards on their board. No guest can delete the board or invite other people.
| Guest role | What they can do on their board | Good for |
|---|---|---|
| Viewer | See every card, comment and attachment, and live changes. Cannot comment, move or edit. | Stakeholders who want status without emails |
| Member | What a workspace member can do on a board: create, edit, move and archive cards, comment, attach files and change columns. | Clients who give feedback, approve work or add requests |
| Admin | Member rights, plus saving and restoring board snapshots. | Rarely needed for clients |
A useful pattern: a Client review column on every client board. Your team moves finished work there, and a member guest moves it to Done or comments what to change. If you need tighter control, keep the client as a viewer and take sign-off in a call or by email.
What does a client see on their board?
A client sees everything on their own board, and nothing on your other boards. Flux has no hidden cards or private comments inside a board. A guest sees every card, comment and attachment on the boards they are invited to. They do not see your other boards, those boards' cards or your workspace settings.
So keep internal work where clients can't see it. A common split is two boards per client: "Acme - Website" shared with the client, and "Acme - Internal" for pricing notes and rough drafts, shared with your team only.
How do you see every client's work in one place?
Use the Multi-Board View in the sidebar. It shows the boards from every workspace you are a member of on one screen, as one kanban board or as a table, so an account manager sees all active clients at once. Boards you are only a guest on are not included, so clients see each of their boards separately under Guest boards.
- Pick the boards. Show or hide each board, or whole workspaces, for example only active retainers.
- Filter across boards by member, label, due date, priority or keyword, for example every card due this week across all clients.
- Name columns the same on every client board. The view merges columns with the same name, so "Client review" from ten client boards becomes one column, and each card shows which board it belongs to.
More detail: Multi-Board View.
How can AI agents work on client tickets?
Connect each agent with its own API key and give it rules for one client board. Agents such as Claude Code, Cursor or Codex reach Flux through the REST API or the Flux MCP server. They can list boards, read cards, create and update cards, move cards between columns and comment. Agents that connect with a member's API key never take a seat.
- Create a key per agent from a team member's account, in Settings under API Keys. Every key can read boards and cards. Tick Write only for agents that change cards. Keys are revocable, with Read-only or Read and Write scopes and an optional expiry date.
- Connect the agent using the Flux MCP server setup. Create agent keys from a workspace member's account: a board guest's key cannot reach a board over MCP.
- Write the board rules into the file the agent reads at the start of each session, such as
CLAUDE.mdorAGENTS.md. A key acts as the person who created it, so the agent can reach every board in every workspace that person is a member of. The rules tell it which client board is in scope. - Review before the client signs off. Agents stop at Internal review, a person checks the work, then moves it to Client review. Clients can see cards in Internal review too, so if drafts must stay private, point the agent at the internal board instead.
An example of step 3, to adapt to your board and column names:
## Client board rules (example) - Work only on the board "Acme - Website". Do not read or change other boards. - Only take cards from "Ready for agent". Move a card to "In Progress" before you start. - Start every comment with your agent name, for example "[copy-agent]". The client reads these comments. - When you finish, comment what you changed and where to check it, then move the card to "Internal review". - Never move a card to "Client review" or "Done".
Two things to know before agents touch a client board. First, an agent's comments appear under the name of the person who created its key, so signed comments tell the client who wrote what. Second, changes made over MCP do not appear in the activity log, so the review step is where your team checks agent work. The rules above are instructions, not locks: Flux does not stop a Write key from moving a card to Done. For the full review-gate setup, see human-in-the-loop for AI agents.
Should each client get a separate workspace?
Usually not. Keep clients as board guests in one agency workspace, so they are not members and not seats. Anyone added to a workspace becomes a member. On Pro and Expert every member is a paid seat, viewers included, and members see every board in that workspace. Each workspace after your first is its own Pro or Expert subscription, and your team would be paid seats in each one.
A separate workspace makes sense when a client wants their own team, members and billing, for example a client who pays for Flux themselves and invites your agency in. The Multi-Board View still shows boards from every workspace you belong to, so you keep one overview either way.
What does Flux cost for an agency?
You pay for your own team only. Board guests and AI agents connected through the API or MCP are never billed. The Free plan has one workspace with one board and unlimited members, enough to try the setup with one client. A board per client needs Pro or Expert, which have unlimited boards and are billed per workspace member. Current prices are on the pricing page.
What doesn't Flux do for client work?
Flux has no public share link, no comment-only role, no hidden cards and no WIP limits, and it does not log MCP changes. In detail:
- No public share link. Clients need a free Flux account with the email you invited.
- No comment-only role. Commenting needs the member role, which can also edit cards.
- No hidden cards. A guest sees every card on their board, so keep internal notes on a separate board.
- No WIP limits on columns. If you cap work in progress per client, agree it as a team practice.
- MCP changes are not logged. Changes made in the app and through the REST API are in the activity log, where undo reverses the latest change to a card or column. MCP changes are not.
Working solo? See Flux for freelancers. Running content for clients? See kanban for marketing teams, with research and drafting agents and an editor review step. For agent-heavy teams, see the kanban board for AI agents.