Create a boundary per client
Use a workspace for each client or team. The portfolio view highlights which needs attention; membership and access checks keep records in their own context.
Preserve review history
Findings, requirements, evidence and reviewer decisions belong to the relevant workspace. Return to a decision without reconstructing it from chat messages.
Check plan limits
Multi-client access is a plan entitlement. Confirm seat limits, client access and export needs before promising a delivery.
Example: one adviser, two client reviews
A DPO adviser handles an HR assistant for Client A and a customer-support bot for Client B. She creates a separate workspace for each, invites the relevant reviewers and records the AI systems and documents in their own context. The portfolio view helps her spot where evidence is missing. When Client A asks for a report, she checks only that workspace's findings and decisions. The separation is a workflow boundary; permissions and exports still need a real account-level test before client delivery.
Set up each client review
- Confirm that the account's plan permits client workspaces and enough seats.
- Name the client workspace, its owner and the people allowed to review it.
- Add the client's systems and documents to the correct workspace before analysis.
- Check evidence, decisions and export scope before sending anything externally.
Common questions
- Which plans can create client workspaces?
- The current plan configuration enables multi-client workspaces for Business, Consultant and Enterprise. Other plans can work in their own workspace but cannot create client workspaces.
- Does a shared adviser account make all clients visible to each other?
- The application scopes records to workspaces and checks membership. Before a sensitive delivery, test the exact invited roles and export path in the live account.
Bring the question into a review
Explore a fictional Fencia walkthrough or tell us which system and evidence your team needs to review.