When someone sends Translation Portal files to Human Review, wxrks creates a review project for them. A project name pattern builds that project's name from the request's details, such as who asked for it, the Organizational Unit (a group inside your account, usually one per client, department or service, with its own prices and settings), the date and the target languages, so your team and your vendors can tell the requests apart at a glance.
💡 Who is this for? Account Admins who manage the Translation Portal.
Before you start
Setting the Account pattern requires Account Admin access.
To set a pattern on an Organizational Unit, a user also needs the Set the Portal project name pattern permission. Account Admins and Project Managers have it by default; you manage it in People > Users > [User] > Permissions, in the Organizational Unit module.
How wxrks picks the project name
You can set a pattern for the whole account and another for any Organizational Unit. When a requester sends files to Human Review, wxrks names the project with the first of these that applies:
The pattern of the Organizational Unit the request is sent to.
The Account pattern.
No pattern: the name the requester types in Project name, or the automatic name
Human Review request - <requester name>when they leave it empty.
A pattern applies to requests sent after you save it. Projects that already exist keep their names.
Set the Account pattern
Go to Settings > Portal & Routing > Portal.
Open the Human Review tab.
In Project name pattern, type the fixed text you want and click a variable under Variables to insert it at the cursor. For example:
{orgUnit} - {name} ({requesterEmail}).Check Name example. It shows the name a request would get, using a sample value for each variable.
Click Save changes.
To stop using the Account pattern, clear the field and click Save changes. Requests then use the typed name again, unless their Organizational Unit has its own pattern.
Variables
Each variable is replaced with the request's details when wxrks creates the project. Hover a variable to see a sample value.
Variable | Replaced with | Example |
| The name the requester types in Project name. If they leave it empty, the name of the first file in the request. | Spring catalog |
| The purchase order entered in PO#. | PO-4521 |
| The email of the user who sends the request. | |
| The name of the user who sends the request. | Jane Doe |
| The name of the Organizational Unit the request is sent to. | Marketing |
| The day the request is sent, as | 2026-03-15 |
| The request's target languages, separated by commas. | de-DE, fr-FR |
ℹ️ Note: {requesterEmail} and {requesterName} always come from the account of the user signed in to the Portal. A requester cannot change them, so the name reliably shows who asked for the review.
A variable with no value, such as {po} when no purchase order was entered, becomes empty text, and repeated spaces collapse into one. If the whole pattern comes out empty, wxrks uses the automatic name.
Set a pattern for one Organizational Unit
Use a unit pattern when one client or department needs a different name than the rest of the account.
Go to Organizations > Organizational Units and open the unit.
Under Setup, click Portal.
Look at Project name pattern. While the unit has no pattern of its own, the field shows the Account pattern in grey, and wxrks tells you where the name comes from:
Inherited from Account: {pattern}, with the Account tag, when the Account has a pattern.
Empty: uses the Account's pattern, or the name the requester types., with the Default tag, when neither level has one.
Type the unit's pattern and insert variables the same way as for the Account.
Click Save changes. The tag changes to This unit: requests sent to this unit now use its pattern instead of the Account's.
To go back to the Account pattern, click Reset to account next to the This unit tag (or clear the field) and click Save changes.
Length limit
The project name can have up to 255 characters.
When you save, the fixed text of the pattern (everything except the variables) must have at most 255 characters.
When a request's values make the name longer than 255 characters, wxrks shortens the
{name}text first, so the requester, unit, date and other details stay readable. If the pattern uses{name}more than once, each one gets an equal share of the room left. Only when the name still does not fit is the end of the name cut.
What requesters and vendors see
Requesters. In the Portal's Human Review window, Project name vendors will see shows the name the project will get, and below it the pattern in use: Pattern set for this org unit or Pattern inherited from the Account. The preview follows the unit chosen in Org unit. If the pattern does not use {name}, the Project name field is turned off, because what the requester types would not be used. See How to send Translation Portal files to Human Review.
Vendors. Vendors see this name as the title of the review project in the My work list on their Home page.
Troubleshooting
"{token} is not an available variable." The pattern has text in braces that is not one of the variables above, for example
{client}. wxrks does not save the pattern. Fix or remove that text, or click a variable to insert it, and save again."The fixed text of the pattern must have at most 255 characters." Shorten the fixed text. Variables do not count toward this limit.
The unit's Project name pattern field is greyed out with "You need the “Set the Portal project name pattern” permission to change this setting." Ask an Account Admin to grant you that permission in People > Users > [User] > Permissions.
A request got the typed name instead of the pattern. Neither the request's Organizational Unit nor the Account had a pattern when the request was sent. Check the unit's Portal section: the tag should read This unit or Account, not Default.