All your files. One project. One context.
Group source files, assign a client profile, and track review progress without jumping between spreadsheets and external tools. Every file inside a project inherits the same Brand Voice, Glossary, and Translation Memory — applied consistently across document types.
Projects in Flixu group source files, a client profile, and quality scoring into a single workspace. Assign a Brand Voice and Glossary at the project level, and every file inside inherits those settings automatically. Translation progress, segment review status, and LQA flags are visible without leaving the workspace.
How projects organize your localization workflow.
A localization project typically involves multiple files, a client-specific context, and a review cycle that distributes across a team. The friction points are predictable: files in different tools, context configured per-file instead of per-project, review status tracked in a separate document, team activity visible only to whoever sent the last email. The project structure addresses each of these as a configuration, not as a workflow management burden.
Create a project and assign a client profile
A project is a named container. When you create it, you assign a client profile — which brings the client's Translation Memory, Glossary, and Brand Voice into scope for the project. That configuration doesn't need to be repeated per file.
Add files to the project
Drop in the source files: .docx, XLIFF, .po, .yaml, .strings, Markdown, JSON, subtitle files. Files of different types can live in the same project. The parser handles each format's structure independently — extracting translatable text, preserving tags and variables, and queuing segments for translation.
Translation runs with inherited context
When translation runs on any file in the project, the client's Brand Voice and Glossary are already loaded. The same approved terminology and tone apply to a product description and a UI string file in the same project — without switching configurations between files.
Review by exception
After translation, the LQA scores determine what appears in the review queue. Segments above the threshold are auto-approved; segments below appear with the specific failing dimension flagged. The review queue shows only what needs attention — not the full document.
→ How LQA scoring and routing works: LQA & Quality Assurance
What the project workspace includes.
Multi-file batching
Add multiple files of different types to a single project. A .docx documentation file, a JSON localization file, and a subtitle file can all be added to the same project and translated with the same client context applied to each.
Project-level context assignment
Assign a client profile at the project level — Brand Voice, Glossary, and Translation Memory scope. Every file added to the project inherits those settings. There's no per-file configuration step; the context travels with the project.
Segment review with LQA flags
The review interface shows source and target side by side with the LQA score visible. Flagged segments include the specific dimension that failed — Terminology Consistency, Formatting, Accuracy, Grammar, or Fluency — so reviewers know what to look at rather than reviewing the full segment from scratch.
Activity feed and audit trail
Every action in a project — translation run, segment approval, string modification, glossary update — is logged in the project activity feed. Team members see what changed, who changed it, and when. The feed provides an audit trail without requiring a separate project management tool.
When project structure changes the workflow.
Translation agencies running multiple concurrent client projects
An agency managing three active client projects simultaneously needs each project's context — TM, Glossary, Brand Voice — to stay isolated and correctly applied without a manual configuration check at the start of each translation run. Client profile assignment at the project level handles that isolation automatically. Translators open the project and the correct context is already active.
For agencies where junior translators or freelance reviewers work alongside the full team, role-based access controls scope what each team member can do: Project Managers configure and approve; Translators run translations and submit for review; Admins manage workspace-level settings.
→ Agency workflows: Flixu for Agencies
→ Team roles and permissions: Team Collaboration
Marketing teams localizing campaign packages
A campaign launch typically involves multiple file types: landing page copy (Markdown or HTML), email sequences (.docx), social copy (JSON or YAML), and sometimes subtitle files for video. Running these through separate tools means configuring Brand Voice separately for each, with inconsistency risk at every handoff.
Grouping the campaign into a single project means one Brand Voice configuration applies to every file. The German landing page, the German email sequence, and the German social posts all come out with the same tone — because they were all translated with the same configuration active.
→ Marketing team workflows: Flixu for Global Marketing Teams
Frequently Asked Questions
Does Flixu have built-in project management for translation?
+
Yes. Flixu includes a project workspace where you can group source files, assign client profiles, track translation progress per file and per language, and monitor segment review status. The project structure handles context configuration and review routing — without a separate project management tool alongside it.
Can I share translation projects with my team?
+
Yes. On Team and Business plans, projects are shared across the workspace with role-based access control. Roles follow the platform's defined permissions: Project Manager, Translator, and Admin. Each role has scoped access — a Translator runs translations and submits segments for review; a Project Manager configures projects and approves output; an Admin manages workspace-level settings including Glossaries and Brand Voice profiles.
Can I mix multiple file types in a single project?
+
Yes. You can add .docx, XLIFF, .po, .yaml, .strings, JSON, Markdown, and subtitle files to the same project. Each file's structure is handled by the appropriate parser — tags, variables, and formatting are preserved per file type. The Brand Voice and Glossary configured at the project level apply consistently across all files regardless of type.
How does the LQA review work inside a project?
+
After translation runs, the LQA layer scores every segment. Segments above the configured threshold — or matching Translation Memory at 99% — are auto-approved without appearing in the review queue. Segments below the threshold appear in the review interface with the specific failing dimension marked (Grammar, Accuracy, Terminology Consistency, Formatting, or Fluency). Reviewers work through the flagged segments; the auto-approved ones don't require their time.
What happens to activity tracking when multiple team members work on the same project?
+
All project interactions are logged in the activity feed: translation runs, segment approvals, string modifications, glossary changes. The feed is visible to all team members with project access. It shows who made each change and when — providing an audit trail without requiring a separate communication channel for status updates.
Is there a limit on the number of files or languages per project?
+
There's no defined cap on the number of files in a project. Projects support all 22+ languages that Flixu covers — you can target multiple languages simultaneously within the same project. Credit usage for translation is visible at the project level, broken down by target language and file.
Start your first project.
Add your files, assign a client profile, and run your first translation. The Brand Voice and Glossary apply to every file from the first string.
Related Features
- LQA & Quality Assurance — Scoring and review routing within projects
- Client Management — Isolated client profiles assigned to projects
- Team Collaboration — Roles and permissions across the project workspace
- Document Translation — File format support and parsing details
- Brand Voice — Tone and style enforcement inherited at the project level