Overview
wxrks lets you set a Sous Chef Agent — a saved combination of audience, tone, formality, creativity, and custom instructions that shapes how AI-assisted translations sound — at three levels: Account, Organizational Unit, and Project. This guide walks through exactly where to configure each one.
For what an Agent actually is, how the three levels cascade, and how it's applied to Context Sensitive translation and the Portal, see Sous Chef Agents.
💡 Who is this for? This guide is for Account Admins and Project Managers who need to configure Sous Chef Agent settings at the account, org unit, and project levels within the wxrks platform.
1. Account level: the global default
The Account-level agent is the fallback wxrks uses whenever an Organizational Unit or Project doesn't have its own agent assigned. Configuring it is limited to Account Admins.
In the left sidebar, open Settings > Translation Settings > Agents. This opens the Augmented Translation Actions page.
On the right side of the page, find the Sous Chef Agent selector, labeled "Select the default agent for this scope (ACCOUNT)".
Pick an existing agent from the dropdown, or click the blue + button to create one. Selecting or creating an agent opens its form below the selector, where you set its Name, Description, Audience (who the translation is for), User Prompt (your instructions to the agent), Formality, Tone, and Creativity Level. Click Save to apply.
The agent currently assigned as the account's fallback carries an Account Default badge in the dropdown list. Only one agent can hold that badge at a time — selecting a different one replaces it.
2. Organizational Unit level: a template for one client or department
An Organizational Unit can inherit the Account's default agent, or use its own — useful when one client or department needs a different tone, audience, or set of instructions than the rest of the account.
In the left sidebar, go to Organizations > Organizational Units and open the unit you want to configure.
Click the Translation Settings tab.
On the right side, find the Sous Chef Agent selector, labeled "Select the default agent for this scope (ORG_UNIT)".
If the selector shows the Account's agent, its fields are read-only here — wxrks displays a note that agents can't be edited at the Account level. To customize it for this Org Unit, click the copy icon next to the selector to clone it into an editable copy, adjust the fields, and Save. The saved copy becomes this Org Unit's Org Unit Default agent, and every project created under it automatically inherits that agent — unless the project sets its own (see below).
3. Project level: the most specific override
The Project level is where an agent actually acts — it shapes every Context Sensitive (CS) suggestion and Pre-Translate result in the Editor for that project.
Go to Projects and open the project you want to configure.
Click the Translation Settings tab.
On the right side, find the Sous Chef Agent selector, labeled "Select the default agent for this scope (PROJECT)".
When a project is created under an Org Unit, this selector automatically defaults to that Org Unit's agent — or to the Account's, if the Org Unit doesn't have one of its own. As at the Org Unit level, an inherited agent shows read-only here; click the copy icon to clone it into a project-specific agent, adjust Audience, User Prompt, Formality, Tone, or Creativity Level as needed, and Save.
Changes apply to new CS suggestions immediately. Segments that were already pre-translated keep their existing output until you re-run Pre-Translate.
How the three levels work together
wxrks always looks for the most specific agent first: Project, then Organizational Unit, then Account. If a project has no agent of its own, it uses its Org Unit's default; if the Org Unit has none either, it falls back to the Account's default.
This is the same cascade used for Portal requests and Paid Review, including how it interacts with a user's own Org Unit selection in the Portal — covered in full in Sous Chef Agents.