-
Phrase TMS (API support)
-
UI access available upon request
Get in touch with Sales or your Customer Success Manager for licensing questions and UI access requests.
Note
Content Groups, Rules, and AI Checks are available in the Phrase user interface upon request: any Platform Administrator or Owner can manage them directly in the product once UI access is enabled for the organization. The full flow also remains available via API for teams that integrate programmatically.
A content group organizes projects by content type, such as marketing copy, UI strings, or legal text. It defines rules and AI quality checks once at the group level, and every project added to the group applies them automatically. This removes repeated per-project setup and the risk of projects drifting out of sync.
What Is a Content Group
A content group is a platform-level, organization-scoped container that projects and language assets are linked to. It represents one type of content that shares the same tone, terminology, and quality bar.
Content that differs in type, such as marketing pages and legal disclaimers, usually needs its own tone, terminology, and quality bar. Previously, this required configuring style guides and quality checks separately for every project. Content groups replace that per-project setup: configure a content type once, and every project of that type inherits it automatically.
Content groups are language-agnostic: a group is not tied to any specific language. Language-specific rules are handled at the rule level, so the same group can apply different rules per language where needed.
How Everything Is Matched: Content Group and Language
Content groups are the single organizing principle across the platform. Everything resolves through the (content group, language) pair.
-
The content side:
Text lives in jobs. Every job carries a language (a source-target language pair, for example,
fr-FRtoen-US). Jobs live in projects, and each project is assigned to exactly one content group, for example, Legal. Because a job inherits its project's content group and carries its own language, every job has a (content group, language) attribution. -
The platform side:
The language assets, rules, and the AI checks derived from them are attributed to content groups and languages.
When an AI capability runs on a job (inside a product or via API), Phrase uses the (content group, language) match to gather every asset attributed to that same pair and apply it automatically. There is no separate quality profile to select and no need to attach guidelines job by job.
Example: A user launches the AI Translation Agent for a French job in a project that belongs to the Legal content group. Phrase gathers all rules attributed to French and Legal and applies them during translation, then uses the AI checks derived from those rules during quality evaluation.
How a Content Group Relates to Style Guides, Rules, and AI Checks
A content group ties language guidance to the projects it governs:
-
Upload a style guide or create rules manually. Phrase extracts a set of rules and links them to the content group, and to a specific language where a rule is language-specific.
-
From each eligible rule, Phrase creates one AI check automatically, a 1:1 mapping.
-
A quality profile is the full set of AI checks for that content group. It matches the group one-to-one and is assigned automatically. It is not built or selected manually.
In short, the content group a project belongs to determines which rules and AI checks apply to it.
Permissions
-
Only users with the Platform Admin or the Owner role can create, edit, and delete content groups and manage the rules and checks inside them.
-
Platform members (for example, TMS Linguists) can view the rules and checks that apply to their content but cannot change them.
Open the Content Groups Overview
From the , click Content groups to display the content groups overview.
Phrase ships with a few predefined content groups (for example, Marketing, UI, and Legal) to avoid starting from an empty state. Use these as they are, rename them, or create new ones.
Create a Content Group
To create a new content group:
-
On the page, click New content group.
The window opens.
-
Enter a .
-
Click Create.
The new group appears as a card on the overview.
Rename or Delete a Content Group
On the group's page, open the More Actions menu next to its name:
-
Select Edit to rename the content group. Renaming a group updates its name everywhere, including on every rule attributed to it.
-
Select Delete to delete the content group.
Caution
Deleting a content group affects its rules.
-
A rule linked only to that group is deleted along with it, and its AI check is deleted too.
-
A rule linked to several groups is kept and only loses its link to the deleted group.
Review a group's rules before deleting the group. Phrase shows a notification before and after the deletion.
-
Open a Content Group's Detail View
Select a group card to open its detail view. Everything that belongs to the group is managed through two tabs:
A project's content group is set directly in the project or project template in Phrase TMS.
To assign a project to a content group:
-
Create or edit a project (or a project template).
-
In the section, select the content group from the dropdown.
The dropdown lists all the organization's content groups.
-
Click through the project settings pages and configure them as needed.
-
Click Create project or Save project if editing an existing project.
A project can belong to only one content group at a time, so there is never ambiguity about which rules apply.
A project's content group can be changed at any time, or removed to leave the project ungrouped.
Tip
If the field is not visible, it may not be enabled for your organization yet. Contact your Customer Success Manager.
Once a project belongs to a content group, translation, post-editing, and quality checks are automated through the group. Style guides and quality profiles no longer need to be added or selected job by job.
Key Things to Know
-
A project can belong to only one content group at a time.
-
A content group can relate to any number of projects.
-
Content groups have a flat structure. There are no subgroups. For subcategories, create standalone groups with descriptive names.
-
Content groups are language-agnostic; the language always comes from the job.
Limits
-
A maximum of 50 content groups can be created per organization.