Client collaboration
Give clients one place to look. Keep the rest of the studio private.
Share the tasks, documents, files and invoices a client needs, then preview exactly what they will see.
Check what the client sees.
Switch to the client view before you send an invite. Internal tasks, candid notes and budgets drop away, and what is left has to make sense to someone outside the team.
Try it on the sample project.
One client, three reasons to log in.
An illustrative website engagement. The same relationship, three people, each arriving for a different decision.
Jess MorrowMarketing manager
The current content task and the brief
Dr. Ravi AnandFounder
The one item waiting on a decision
Owen ClarkeFinance
The invoice and what it is for
The client side
Your brand. Their work. Nothing else.
Clients follow the project in a separate experience with its own access, and portal users do not need paid team seats.
Your name, logo and color
Clients land somewhere they recognize as yours.
Only the tasks you share
Project and task visibility decide what appears.
Comments next to the work
Clients reply on the tasks you make visible to them.
Documents that stay readable
Client-visible briefs and decisions, current version first.
Files in one place
Shared files sit with the project they belong to.
The invoice with its project
Finance finds the amount and the work it covers together.
Clear about what the portal shows.
What the portal does
- Gives clients free access, separate from your team members.
- Carries your agency name, logo and accent color.
- Shows the tasks, documents, files and invoices you choose to share.
- Lets you preview the client experience before you invite anyone.
What it does not do
- Run on your own domain. Full white-label and custom domains are not available.
- Show proofs. Share a review file on a client-visible task instead.
- Check a file you upload yourself. Read shared documents before inviting a client.
Tell the client where feedback goes and where final decisions are recorded, then keep that instruction the same every time. See how proofing fits in ↗
The details.
Everything above, in depth. Open what you need.
Design the client experience around a decision
Start with the question the client is trying to answer. They may need to review a task, find a document, supply a missing file, or inspect an invoice. A useful portal makes those actions easier to locate. It should not become a second collection of loosely named files that someone still has to explain by email.
Project and task visibility determine which work appears externally. Keep internal planning, candid team discussion, and commercial information in their proper scope. Client-visible documents and shared files can provide the context needed to act without exposing the entire internal workspace. A clear title and a short explanation often do more for client confidence than sharing a large quantity of material.
Use client access deliberately
Portal users are distinct from internal team members. Flowboard's offering includes free client access, which supports inviting relevant client stakeholders without treating each reviewer as a paid internal operator. That distinction does not mean every person should receive the same view. Associate people with the right client and project context, and review access as relationships change.
Add your agency name, logo, and accent color to give clients a recognizable place to collaborate. These branding controls shape the portal's appearance. Full white-label infrastructure and custom domains are not currently available.
An illustrative review with three stakeholders
Imagine a website engagement with a marketing manager, a founder, and a finance contact. The marketing manager needs the current content task and the brief. The founder needs to understand the item awaiting a decision. Finance needs the invoice and payment context. They belong to the same client relationship, but their reason for visiting is different.
Before inviting them, preview the portal as the client. Confirm that the current document is visible, internal notes remain internal, the task explains the requested action, and the invoice is linked to the right project. Organize the shared material around the decisions those stakeholders need to make.
| Client need | Prepare in Flowboard | Check from the client view |
|---|---|---|
| Understand the brief | Client-visible document | The current version is clear |
| Review the work | Visible task and supporting files | The requested decision is explicit |
| Discuss an issue | Client conversation context | The right project is recognizable |
| Handle payment | Relevant invoice | The amount and next action make sense |
Launch a portal without creating another support burden
A short setup review helps the portal become a useful habit. Test with a representative engagement before moving every client conversation into a new place.
Choose the shared project context
Identify the client and the work they should follow. Remove confusing or obsolete material from the intended client-facing path.
Set visibility on the actual content
Choose the tasks, documents, and files to share. Keep internal planning notes and cost information within the team, and make the next client action clear.
Preview the client experience
Use the available client preview to check navigation, visible content, and the next action. Look for missing context as well as accidentally shared detail.
Explain the collaboration habit
Tell the client where to leave feedback, where final decisions belong, and how invoices will be handled. Keep that instruction short and consistent.
Give feedback a clear next step
Clients can comment on the tasks you make visible to them, which keeps their feedback next to the work. Your team manages file versions, image annotations and approval decisions in the proofing workspace, which clients do not see. Preview the client experience before sending an invitation.
Name the person responsible for each approval and tell them where to record it. Keep the requested decision clear, especially when it affects scope, deadlines, or payment. That gives both your team and the client a dependable next step.
Share the brief and decisions
Use client-visible documents for context that needs to stay readable over time.
Explore this workflow ↗Structure creative review
Understand file versions, image annotations, and proof review limits.
Explore this workflow ↗Questions
Before you invite the first client.
Do clients need paid team seats?
Flowboard distinguishes portal users from internal members and offers free client access. Use internal membership for people operating inside the agency workspace, and client access for the external collaboration experience. Check the current pricing terms when configuring your team.
Will a client see our internal cost rates?
The client portal is a separate experience with visibility controls. Internal financial values and staff cost rates are not content to expose through a shared brief or file. Review the client view and the material you upload, since manually shared documents can themselves contain sensitive information.
Can the portal carry our agency branding?
Yes. You can use your agency name, logo, and accent color. Full white-label infrastructure and custom domains are not currently available.
Can clients approve work?
Clients can reply on the tasks you share with them, so they can confirm a decision in the task comments. The portal does not currently offer a separate approve button or access to proofs. Define what a written approval means in the engagement and record it against the task.
What should we test before inviting a client?
Check the correct client association, project visibility, documents, files, task wording, and invoice context. Use a client preview and ask whether an external person could understand the next action without a walkthrough. Repeat the review when the engagement or access requirements change.