A Sous Chef Profile is a saved set of instructions for wxrks' AI translation: who the content is for, how formal it should be, its tone, how creative the AI can be, and your own written brief. This guide shows you how to create profiles, choose which one applies by default, route specific language pairs to a different profile, and set profiles for one Organizational Unit or one project. It also explains how wxrks decides which profile wins when several could apply.
Who is this for?
Account Admins manage the Sous Chef Profiles page: creating and deleting profiles, the account default, Organizational Unit assignments, and language pair mappings. Only the Account Admin role sees that page.
Project Managers choose the profile for an Organizational Unit or a project from its Translation Settings tab. Account Admins can use both tabs too. The Organizational Unit tab also needs the Organizational Unit Update permission.
Before you start: A profile only affects output when AI translation is on. That's the Enable Augmented Translation Actions setting, covered in wxrks Augmented Actions. For what a profile changes in the AI output, see Sous Chef Agents Explained. Older articles call profiles "Sous Chef Agents"; it's the same thing.
Key concepts
Term | What it means |
Scope | Where a profile is set: the whole account, one Organizational Unit, one project, or one work unit (a single document in a project). |
Default | The profile a scope uses for every language pair that doesn't have its own mapping. Each scope has at most one default. |
Language pair mapping | A rule that sends one exact source → target pair, such as English (United States) → Portuguese (Brazil), to a specific profile. You can map a pair for the whole account or for one Organizational Unit. |
How wxrks picks the profile
For each document, wxrks checks the scopes from the most specific to the most general and uses the first profile it finds. Within a scope, a mapped language pair beats that scope's default:
Work unit: a profile set for that one document in the editor.
Project: a mapping for the document's language pair, then the project's default.
Organizational Unit: a mapping for the language pair, then the Organizational Unit's default.
Account: a mapping for the language pair, then the account default.
If nothing matches anywhere, the AI translates without a profile.
The Sous Chef Profiles page sums this up in one line, under both headings: "Most specific scope wins; within a scope, a mapped pair beats the default." Hover the info icon next to it to see the full order.
Worked example
Your account has these settings:
Setting | Profile |
Account default | General Marketing |
Account mapping: English (United States) → Japanese | Game UI Strings (JP) |
Default of the Organizational Unit Acme Legal | Legal Compliance |
Acme Legal mapping: English (United States) → Portuguese (Brazil) | Technical Documentation |
This is what each document gets:
Document | Profile applied | Why |
Acme Legal project, English (United States) → Portuguese (Brazil) | Technical Documentation | The Organizational Unit's own mapping is the most specific match. |
Acme Legal project, English (United States) → Japanese | Legal Compliance | The Organizational Unit's default outranks the account's mapping. The account mapping never applies inside Acme Legal. |
Project in another Organizational Unit with no default, English (United States) → Japanese | Game UI Strings (JP) | No project or Organizational Unit setting matches, so the account mapping is next. |
Same project, English (United States) → German | General Marketing | Nothing more specific matches, so the account default applies. |
⚠️ Common misconfiguration: An account mapping doesn't reach an Organizational Unit that has its own default. In the example, if Acme Legal also needs Game UI Strings (JP) for Japanese, map English (United States) → Japanese at the Acme Legal scope too.
ℹ️ Note: Mappings match the exact locales. An English (United States) → Portuguese (Brazil) mapping doesn't apply to English (United States) → Portuguese (Portugal), or to English (United Kingdom) → Portuguese (Brazil).
Open the Sous Chef Profiles page
In the sidebar, go to Settings > Translation Settings > Sous Chef.
The Sous Chef Profiles page opens. On the left, the Profiles list shows every profile with its formality, tone, creativity, and the flags of any language pairs mapped to it. The account default carries a Default badge. Select a profile to see its details in the panel on the right. Selecting a profile only shows it; it doesn't change anything.
Use Search profiles to filter the list by name.
Create a profile
Click New profile.
Fill in the form:
Name (required, up to 100 characters). Must be unique in your account.
Description (optional, up to 300 characters). A short note that explains when to use the profile.
Domain (required). The subject of the content, for example Contracts and regulatory filings.
Audience (required). Who will read the translation, for example Legal counsel and compliance officers.
Formality (required): Informal, Neutral, or Formal.
Tone (required): Professional, Conversational, Persuasive, Technical, Witty, Direct, or Artistic.
Creativity: a slider from 1 (most literal) to 5 (most inventive). It starts at 3.
Instructions (required, up to 5,000 characters). Plain text the AI follows for every segment translated with this profile, such as brand voice, terminology rules, or examples.
Click Save.
Domain, audience, formality, and tone are required because they give a profile its own point of view. Instructions alone don't tell the AI who it's writing for.
ℹ️ Note: A counter under each text field shows how many characters you've used. If a field goes over its limit, it turns red and Save stays disabled until you shorten it. wxrks never cuts your text silently.
To start from an existing profile, select it and click Duplicate. The form opens with the same settings and (copy) added to the name, for example "Legal Compliance (copy)".
To change a profile, select it and click Edit. Changes apply everywhere the profile is used.
Set the account default
The account default is the fallback for every project that has no more specific match.
Select the profile in the Profiles list.
Click Set as default.
The profile gets the Default badge and moves to the top of the list. Only one profile can be the account default, so setting a new one replaces the previous one.
To remove the account default, select the profile that has it and click Clear default, then confirm. After that, projects and Organizational Units with no profile or mapping of their own run without a Sous Chef Profile.
Assign a profile to Organizational Units
Use this when a client or department needs its own instructions for all of its projects. You can assign one profile to several Organizational Units at once.
Select the profile and click Assign to org units below its details.
Pick one or more Organizational Units.
Click Save.
If any of the Organizational Units you picked already defaults to another profile, a warning lists each one with the profile it uses now, for example "Docs OU (article-helper) (currently Technical Documentation)", before you save. Saving switches them to this profile.
Map a language pair to a profile
Use a mapping when one language pair needs different instructions from the rest of its scope, for example a Japanese UI style guide while every other language uses the default.
Open the New mapping window in either of two ways:
Select the profile and click Map a language pair below its details. The window opens with that profile already chosen.
Scroll to Language Pair Mappings below the profile list and click New mapping.
Under Scope, choose Whole account, or choose Org unit and pick the Organizational Unit.
Under Profile, choose the profile to use.
Choose the Source and Target languages.
Click Save.
Each scope can map a given pair only once. If the pair is already mapped in that scope, wxrks doesn't save the new mapping and shows "This language pair is already mapped for this scope". To send that pair to a different profile, edit the existing mapping instead.
The Language Pair Mappings table lists every mapping in your account, Organizational Unit mappings first. To change which profile a mapping uses, click its pencil icon. Scope and languages can't be edited: to change them, delete the mapping with the trash icon and create a new one.
Check where a profile applies
Select a profile and look at Where this profile applies in its detail panel. The table lists every place the profile is the default or is mapped to a pair. Its rows are in the same order wxrks checks them: Organizational Unit mappings, then Organizational Unit defaults, then account mappings, then the account default.
Scope: Account or Org unit.
Where: the Organizational Unit's name, or Whole account.
Applies for: Default, or the mapped language pair.
To stop using the profile somewhere, click the × at the end of that row and confirm.
If a project or a work unit chose this profile directly, a line under the table says so, for example "Also picked directly by one project and 0 work units." Those choices are made in the project or the editor, so they don't appear in the table.
Delete a profile
Select the profile and click Delete.
Read the confirmation, which lists everything you'll lose:
whether it's the account default (nothing replaces it),
which Organizational Units lose it as their default, and whether they fall back to the account default or run without a profile,
how many language pair mappings are removed with it,
how many projects and work units chose it directly.
Click Delete.
⚠️ Warning: Deleting a profile removes it from every scope and mapping that uses it. This can't be undone.
Set the profile for one Organizational Unit
Project Managers can do this from the Organizational Unit itself, without the Sous Chef Profiles page.
In the sidebar, go to Organizations > Organizational Units and open the Organizational Unit.
Click the Translation Settings tab.
On the right, find Sous Chef Profile ("Select the default profile for this scope (ORG_UNIT)") and choose a profile. Your choice is saved as soon as you pick it.
The profile you choose becomes this Organizational Unit's default. Every project in it uses it unless the project sets its own.
If the Organizational Unit has no default of its own, a hint under the selector shows the profile it inherits, for example "Inherited default (Account): General Marketing".
To customize a profile for this Organizational Unit only, click the copy icon (Duplicate profile), adjust the fields, and save. The copy belongs to this Organizational Unit, so the original stays unchanged everywhere else. To start from scratch, click the + icon (New profile).
ℹ️ Note: A profile from the account's Sous Chef Profiles page is shared by the whole account. Only Account Admins can edit or delete it. Everyone else duplicates it to customize it.
Below the selector, the Language pair overrides card lists the mappings that win over this Organizational Unit's default:
Mapped in this org unit: these replace the default for their pair.
Mapped at the account: these apply only while the Organizational Unit has no default of its own.
Account Admins also see a Manage mappings in Settings > Sous Chef Profiles link. Mappings are created and edited only on that page.
Set the profile for one project
Go to Projects and open the project.
Click the Translation Settings tab.
On the right, find Sous Chef Profile ("Select the default profile for this scope (PROJECT)") and choose a profile. Your choice is saved as soon as you pick it. As on the Organizational Unit tab, you can duplicate an inherited profile or create a new one.
A project's choice outranks its Organizational Unit and the account. The new profile applies to Context Sensitive suggestions right away. Segments that were already pre-translated keep their output until you run Pre-Translate again. For the other settings on this tab, see Project's Translation Settings.
ℹ️ Note: Linguists can also choose a profile for the single document they're translating, from the Sous Chef Profile tab in the editor. That choice outranks everything above, but it doesn't change the project or any other document. See How to check and change the Sous Chef Profile for a document in the editor.
Troubleshooting
What you see | Why | What to do |
A project uses a different profile than you expected | A more specific scope or mapping matches first | Walk through the order in How wxrks picks the profile above. Check the project's Translation Settings tab and the Organizational Unit's Language pair overrides card. |
An account mapping is ignored in some projects | Their Organizational Unit has its own default, which outranks account mappings | Map the same pair at that Organizational Unit's scope. |
A profile with this name already exists. | Profile names are unique in the account, ignoring capitalization | Choose a different name. |
Save stays disabled in the profile form | A required field is empty, or a field is over its character limit | Fill in the fields marked as required and shorten any field whose counter is red. |
This language pair is already mapped for this scope | That scope already has a mapping for the same source and target | Edit the existing mapping in Language Pair Mappings to point it at the profile you want. |
This profile no longer exists | Someone deleted the profile while you were editing it | The list reloads. Create the profile again if you still need it. |










