Agents vs. Sous-Chef
Sous-Chef is the interface where you control how translations sound — tone, audience, formality, creativity, and custom instructions. Agents take those same settings and make them reusable, assignable, and automatic.
With Sous-Chef alone, settings had to be applied manually and worked at a segment level. Agents solve that by letting you define configurations per Account, Organization Unit or project and apply them without any manual steps.
How Agents works: the 4-level hierarchy
Agents operate in a cascade, wxrks looks for the most specific configuration available and applies it. If none is found at that level, it falls back to the next one up.
The hierarchy works as follows:
System Prompts — wxrks' default baseline, always active in the background.
Account Default Agent — your account-wide fallback when no other Agent is assigned.
Org Unit Default Agent— the Agent defined at the Organizational Unit level. All users and projects associated with that Org Unit inherit this configuration automatically.
Project Agent — the most specific level. When assigned to a project, it takes full priority over everything above.
Agents are applied to every Context Sensitive translation
This is an important shift from how wxrks worked before. Agents are no longer just an optional configuration layer — they are now part of every translation that goes through Context Sensitivity (CS).
This means that whenever wxrks generates a CS suggestion, blending Translation Memory, Machine Translation, and Glossary into a single intelligent output, an Agent is always active behind it, shaping how that output sounds. The Agent's tone, audience, formality, creativity, and instructions influence every segment the AI touches, not just when explicitly triggered.
Agents and the Portal
The Default Org Unit:
Every translation request made through the Portal is processed using the configuration of an Org Unit: its Agent, Translation Memory, Paid Review settings, and Price List. Knowing which Org Unit applies to a given user is essential to understand why the Portal behaves the way it does.
Step 1: the account-level Portal Org Unit
The starting point is set by your account administrator in Tools → Portal. This is the account-wide default Org Unit — the fallback configuration used for any Portal user who doesn't have a more specific Org Unit assigned.]
Step 2: prioritizing the user's own Org Unit
Administrators can enable an option called Prioritize user's Default Portal Organizational Unit. When this is active, wxrks checks whether the user has a personal Org Unit assigned before falling back to the account default.
The logic works as follows:
If the user belongs to only one Org Unit, that unit is used automatically.
If the user belongs to multiple Org Units — or has none assigned — the system falls back to the account-level Portal Org Unit set in Step 1.
How to assign a personal Org Unit to a user
There are two ways to create this association:
Via the Org Unit — Portal Access Management Inside the Org Unit settings, there is a section called Portal Access Management. Users added here will have that Org Unit set as their Portal default — meaning their requests in the Portal will automatically use that unit's Agent, TM, and Paid Review settings.
Via the user profile — Associations tab In the user's profile, under the Associations tab, there is a field called Organizational Unit for Portal Management. Setting this field assigns that Org Unit as the default for all of that user's Portal activity.
Both methods produce the same result. Use whichever fits your team's workflow.
Association rules
wxrks enforces a strict relationship between users and their Portal Org Unit:
One Org Unit → many users. A single Org Unit can be the Portal default for multiple users.
One user → one Org Unit only. A user can only have one Portal default Org Unit at a time. If a new association is set, it replaces the previous one automatically.
This strict rule prevents conflicting configurations when a user logs into the Portal.
Overriding the default: user-level Org Unit selection
Users with the permission User Select Org Unit in Portal can manually switch their active Org Unit directly from the Portal interface using a dropdown. This overrides whichever default would have been applied and lets them choose which Agent and TM to use for each request.
This is useful for project managers or power users who handle content for multiple clients or brands, each with distinct voice requirements.
Paid Review and the auto-generated Agent
When a user submits a Paid Review request through the Portal, wxrks does something important: it automatically creates a dedicated Agent for that specific project, labeled Custom AI Agent - P-[Project ID].
This isn't just a copy of the Org Unit Agent. It's a snapshot — a frozen version of the exact configuration at the moment of submission. This means:
The instructions, tone, audience, and formality settings are locked in for that project.
Any future changes to the Org Unit Agent won't affect a review already in progress.
Reviewers working on that project always have a clear, stable AI baseline to work from.