Flixu
Feature Spotlight

Built for teams.
Not just individuals.

Shared Translation Memories, Glossaries, and Brand Voices across your entire team. Role-based access so freelancers and contractors see only what they need. One workspace, consistent terminology, clear accountability.

What is Team Collaboration in Flixu?

Team and Business plans let multiple users share Translation Memories, Glossaries, and Brand Voice configurations within a single workspace. Role-based access controls scope what each team member or external contractor can view, edit, or approve. When any team member confirms a translation, it updates the shared Translation Memory — available to every user in the workspace.

Role-based access control.

Three roles cover the range of team structures — from the workspace administrator who configures everything to the contractor who reviews a single project:

Role What they can do
Admin Full workspace access: manage billing, configure global settings, create and delete client profiles, edit Glossaries and Brand Voice profiles, manage team members, invite and remove users
Project Manager Create and configure projects, assign client profiles, run translation workflows, review and approve segments, monitor progress across the workspace
Translator Work within assigned projects: upload files, run translations, edit and submit segments for review. Cannot modify global Glossaries, Brand Voice settings, or client configuration

Note: These are the platform's current defined roles. Check the documentation for the latest role permissions as the platform evolves.

For teams that include external contractors or freelancers, role assignment at the project level means they see the projects they're invited to — not the broader workspace, client list, or global configuration settings.

How shared workspaces work.

The practical value of a shared workspace is that individual actions compound. When one translator confirms a segment, every subsequent translation for that client benefits from that approved phrasing — in full projects and in Quick Translate.

1

Shared Translation Memory

All confirmed translations within a client workspace update the shared Translation Memory. When Translator A confirms "Submit" as "Absenden" for a client, Translator B working on a different document for the same client sees that as a style reference. The workspace's quality improves with each approved segment, regardless of who confirmed it.

2

Shared Glossary and Brand Voice

Changes to a client's Glossary or Brand Voice configuration are immediately active for all projects under that client. An Admin who adds a new approved term to the Glossary doesn't need to notify the team — the next translation run for any team member working on that client will apply the updated constraint.

3

Project-level assignment and visibility

Projects can be assigned to specific team members. A Project Manager assigns files to a Translator; the Translator sees their assigned projects and works within them. The Admin and Project Manager see progress across all projects in the workspace.

4

Activity feed and audit trail

Every action in the workspace — segment confirmed, Glossary updated, Brand Voice changed, file translated — is logged in the activity feed. Project Managers can see what changed, who changed it, and when, without a separate communication thread.

What team collaboration includes.

Shared Translation Memory

Every confirmed translation updates the shared TM for that client workspace. New translations for the same client benefit from previous approvals — across all team members, all projects, all file types.

Role-based access control

Three roles — Admin, Project Manager, Translator — scope workspace access appropriately for internal teams and external contractors. Freelancers assigned as Translators work within their projects without accessing global configuration.

Activity feed

Every segment confirmation, file upload, Glossary change, and project creation is logged in real time. Project Managers and Admins see team activity without needing status updates sent separately.

Unified workspace billing

Your workspace's translation credits are shared across all team members. One account, one credit pool, one invoice. Usage is visible at the project and workspace level — broken down by file and target language.

When team structure changes the outcome.

Agencies running projects with in-house and freelance translators

An agency with three in-house translators and a rotating roster of project-based freelancers needs access control that keeps each group appropriately scoped. In-house staff with Admin or Project Manager roles configure client settings and review output; freelancers assigned as Translators work within their assigned projects without seeing other clients or global configuration. Role assignment at the project level handles this without a separate permission system.

The shared Translation Memory is where the team's quality compounds: every confirmation by any team member improves the style reference pool for every subsequent translation for that client. The more the team works, the more consistent the output.

→ Agency workflow overview: Flixu for Agencies

Marketing teams with distributed global reviewers

A marketing team localizing campaigns in-house often involves native-speaking regional reviewers who check cultural accuracy, not the full localization pipeline. Assigning regional reviewers as Translators gives them access to review and approve translated output for their language pair — without exposing Brand Voice configuration or Glossary management to every reviewer.

→ Marketing team workflows: Flixu for Global Marketing Teams

Enterprise localization programs with compliance requirements

For regulated content — legal, medical, financial — the activity feed provides an audit trail of who approved what and when. The documented approval chain is accessible to Admins and Project Managers without requiring a separate compliance logging system.

→ Enterprise workflows: Flixu for Enterprise

Frequently Asked Questions

How does shared Translation Memory work across team members?

+

When any team member confirms a translated segment in a client workspace, that approved translation becomes part of the shared Translation Memory for that client. The Semantic Reranker retrieves it as a style reference for subsequent translations — whether run by the same translator or a different one. Confirmed translations from any team member improve the quality pool for everyone working on that client.

Can I restrict what my freelance translators can see?

+

Yes. Translators assigned to a project see only that project — not other client workspaces, global Glossary settings, Brand Voice configurations, or billing information. You can invite external contractors as Translators for specific projects, and their access is scoped to those projects only.

What are the three roles and what can each do?

+

Admin: full workspace access including billing, global settings, and user management. Project Manager: create and configure projects, run translations, review and approve segments, monitor workspace progress. Translator: work within assigned projects — upload files, run translations, edit and submit segments. Translators cannot modify global Glossaries, Brand Voice profiles, or client settings.

Can a team member be upgraded or downgraded between roles?

+

Yes. Admins can change any team member's role at any time through the workspace settings. A Translator can be promoted to Project Manager; an external contractor who no longer needs edit access can be downgraded. Role changes take effect immediately.

Does Translation Memory update in real time when a team member confirms a translation?

+

Yes. Confirmed translations update the shared TM for that client workspace immediately. There's no batch sync or delay — the next translation run for any team member working on the same client will have access to the latest approved phrasing.

How is billing handled for a shared team workspace?

+

The workspace has a shared credit pool. Credits are consumed by translations run by any team member — the pool isn't per-user. One invoice covers the workspace's total translation volume. Admins can see credit usage broken down by project and language in the workspace settings.

Scale your team without losing consistency.

Invite your team, assign roles, and share Translation Memory and Glossaries across every project from day one.

Related Features