One workspace. Multiple clients. Zero terminology crossover.
Each client brings their own approved terms, tone of voice, and translation history. The Client Management layer keeps all of it separated — so the legal terminology from one client never appears in the marketing copy of another.
Client Profiles are isolated workspaces within a single Flixu account. Each profile holds a dedicated Translation Memory, Glossary, and Brand Voice configuration for that client. When a translator opens a project, the correct context is already loaded — no manual switching, no risk of carrying a term from one client into another client's content.
How Client Management organizes your workspace.
For agencies and multi-brand teams, the core problem is isolation: keeping Client A's approved terminology from drifting into Client B's output, without requiring the translator to manually check which glossary is active on each project. Client Management works through three structural layers:
Create a client profile
Each client gets a dedicated profile in the workspace: a named entity that holds their Translation Memory, Glossary terms, and Brand Voice configuration. The profile is the container — everything that belongs to that client lives inside it and applies only to projects assigned to it.
Assign assets to the profile
Upload the client's approved translations as Translation Memory, add their approved terminology to the Glossary, and configure their Brand Voice if they have tone requirements (formal register for a law firm; casual and direct for a consumer app). Each asset is scoped to that client — it won't appear in or influence translations for any other client.
Open a project and work
When a team member opens a project assigned to a client profile, the correct TM, Glossary, and Brand Voice are already active. The translator doesn't configure anything — the context was loaded when the project was created. The system enforces client-specific rules from the first string.
→ How Brand Voice configuration works:
Brand Voice Manager
→ How Glossary constraints are applied:
Glossary Enforcement
What each client profile contains.
Isolated Translation Memory
Each client's approved translations are stored in a separate Translation Memory. The semantic retrieval layer only searches within the assigned client's TM — a legal term approved for one client will never surface as a suggestion for another client's project.
Brand Voice Assignment
A specific Brand Voice profile attaches to each client. When a translator works on that client's content, the brand voice configuration is applied to every translation request automatically — no manual step required, no risk of using the wrong tone for the wrong client.
Centralized Glossary per Client
Each client's Glossary — approved terms, forbidden words, required capitalizations, product names — is mapped at the client level, not the document level. A term added to Client A's Glossary applies to every project under that client's profile.
Activity and Volume Tracking
Translation volume is tracked per client profile, giving agencies visibility into output by client for internal reporting. On Business plans, API tokens can be scoped to individual client profiles — backend calls automatically route to the correct TM, Glossary, and Brand Voice without specifying them per request.
When client isolation changes the workflow.
Translation agencies managing five or more active clients
When an agency runs multiple clients through a single workspace without client-level isolation, the practical risk is terminology drift. An approved medical term from a pharma client appears in TM suggestions for a consumer brand. A formal tone setting leaks into a casual app translation. These aren't rare edge cases — they're the predictable consequence of a flat workspace structure.
Client profiles eliminate this by design. The workspace sees multiple clients; each translator sees only the context that belongs to the client they're working on. No configuration reminder before each project, no manual check that the right glossary is loaded.
→ Agency workflows and multi-client management: Flixu for Agencies
Multi-brand marketing teams
A marketing team managing localization for three product lines — each with different brand voices, different approved terminology, and different regional requirements — faces the same isolation problem within a single company. Client Management handles multi-brand setups the same way it handles multi-client agency setups: each brand is a profile, and its assets are scoped accordingly.
→ Global marketing team workflows: Flixu for Global Marketing Teams
Development teams with per-client API integrations
On Business plans, API tokens can be issued and scoped to individual client profiles. A backend call using a specific token automatically loads the corresponding client's Translation Memory, Glossary, and Brand Voice — without passing those parameters explicitly in each request. For agencies with developer teams building localization into client-facing pipelines, that scoping eliminates a layer of per-call configuration.
// Conceptual illustration — actual API parameters in the documentation
{
"client_id": "cli_example_a1b2",
"source_text": "Please review the contract terms.",
"enforce_glossary": true
}
// Routes to Client A's Translation Memory and Glossary automatically
→ Developer API details: Developer API
Frequently Asked Questions
How does Flixu keep client translation memories from affecting each other?
+
Each client profile has its own isolated Translation Memory. When the Semantic Reranker searches for past approved translations to use as style references, it only searches within the TM assigned to the active client profile. There's no shared pool across clients — terminology approved for one client is not retrievable in another client's context.
Can I assign different brand voices to different clients?
+
Yes. You can create as many Brand Voice profiles as you need and assign one to each client. When a project is opened under a client profile, that client's brand voice is applied to every translation request automatically. You're not limited to one voice per account — each client can have distinct tone, formality, and style parameters.
Is there a limit to how many clients I can manage?
+
There's no cap on the number of client profiles you can create or manage within a Flixu workspace, regardless of subscription tier.
How do API tokens work with multiple clients?
+
On Business plans, you can generate API tokens scoped to individual client profiles. A backend call authenticated with a client-specific token automatically routes to that client's Translation Memory, Glossary, and Brand Voice — without requiring those parameters in each API request. This is the intended setup for agencies building localization into automated client-facing pipelines.
If I update a client's Glossary, does it apply to all future translations for that client?
+
Yes. Glossary changes at the client profile level apply to all subsequent translations under that profile. Existing approved translations in the Translation Memory are not retroactively changed — they remain as previously approved. New translations run after the update will apply the new or modified glossary terms as constraints.
Can multiple team members work on the same client profile simultaneously?
+
Yes. Client profiles support the full Team Collaboration feature — multiple translators, project managers, and reviewers can work within the same client profile with role-based access control. A Translator sees their assigned projects; an Admin can manage the Glossary and Brand Voice settings.
Set up your first client profile in under five minutes.
Create a profile, upload a glossary, assign a brand voice. Every project you create under it inherits that context automatically from the first string.
Related Features
- Brand Voice Manager — Tone and formality configuration per client
- Glossary Enforcement — Terminology constraints scoped to client profiles
- Translation Memory — How isolated TM retrieval works per client
- Team Collaboration — Role-based access across client workspaces
- Flixu for Agencies — Multi-client workflow overview