Settings is where an Account Admin configures how the whole wxrks account behaves: plan and branding, sign-in and security, translation defaults, AI, automation, client intake and billing. This article explains how Settings is organized, how to find and save a setting, and what each page is for, with links to the in-depth article when there is one.
💡 Who is this for? Account Admins. Other users only see the Settings pages their permissions allow; for example, a user who can create projects sees Project routing.
Open Settings and find your way around
Click the gear icon in the left rail to open Settings. It opens on Account > Plan & Usage.
Use the Settings menu to move between pages. Pages are grouped by subject: Account, Identity & Security, Translation, AI, Automation, Portal & Routing and Finance & Billing. Click a group to expand it.
Each page starts with a one-line description of what it controls. Longer explanations sit behind the info icon next to a setting, and complex features have a Learn more link to their Help Center article.
Search for a setting
You don't need to know which group a setting is in. Type its name in Search projects, files and settings at the top of the screen; the Settings results show where each match lives, for example Account › Custom fields, and whether it belongs to the account, an organization or an Organizational Unit.
ℹ️ Note: Bookmarks and links to the old Settings pages still work: they open the matching page in the new layout.
Save your changes
Settings saves in one of two ways, depending on the control:
Forms with a Save button. When you change a field, a bar appears at the bottom of the page with Unsaved changes and the page's save button, for example Save due dates. Nothing is saved until you click it. If you leave the page first, wxrks warns you.
Switches that save right away. Some on/off switches, such as the ones on Translation > General, apply the moment you click them. No bar appears.
Settings that open in their own window, or that edit one item at a time (for example, a single price list), keep their own save button inside that window.
What each page does
Account
Page | What it controls |
Plan & Usage | Your plan and what the account consumes. Nothing here changes how the product behaves. See How to update and manage your wxrks plan. |
Branding & Domains | The account logo and the domain your users and clients reach wxrks on. Domain and certificate changes can take up to 72 hours. |
Hierarchy | How organizations and Organizational Units are structured, as a diagram or a list. See Accounts, Organizations and Organizational Units. |
Custom fields | Extra fields for projects, users, organizations and Organizational Units. See All About Custom Fields. |
Organizational Unit template | The values new Organizational Units start with. When you save, you choose whether the changes also apply to existing units. See All about Organizational Units. |
Identity & Security
Page | What it controls |
Single sign-on | Sign-in with your identity provider: Okta, OneLogin, Azure AD (Microsoft Entra ID) or SAML 2.0. See wxrks Single Sign-On (SSO). |
User provisioning | Create and manage user accounts automatically from your identity provider, through SCIM or SAML Just-in-Time. See SCIM User Provisioning Reference. |
Security policies | Account-wide rules for sign-in, sessions and passwords. |
Translation
Page | What it controls |
General | Which languages people can pick, the project quote report, and the reasons a project can be canceled for. |
Language aliases | Other names your files use for a language, such as "Mexican Spanish", so wxrks recognizes them. |
Workflows | The workflows projects follow, their steps, and which workflow each file type gets. See Managing your custom workflows. |
Machine translation | MT engines and credentials. A language-pair setting beats the default, and an Organizational Unit setting beats the account. See Connect a Machine Translation (MT) provider. |
Segmentation | The SRX rules that split text into segments, one active rule per language and file type. See All about segmentation rules. |
Filter settings | How each file type is parsed. An Organizational Unit without its own default for a file type uses the account default. |
Smells Scoring | How the AI quality check (Translation Smells) scores a translation: how much each severity weighs, which severity each kind of smell gets, and when a segment is confirmed. |
Quality & Review | Automatic QA checks and how reviewers categorize changes. See How to use the wxrks QA Check Tool. |
Quotation marks | The quotation marks of each target language: a Default row plus a row for each language whose marks differ. Also the default of Smart quotation marks while typing, which each linguist can still turn on or off in the Editor. See How to use smart quotation marks for each target language. |
Editor preferences | Shared sets of Editor translation preferences that Organizational Units and projects can use. Shown when it is enabled for your account. |
Terminology Board | How new terms move from suggestion to approval. See The Terminology Board. |
Glossary Required Fields | Which term fields must be filled before a term is saved in each glossary. |
AI
Page | What it controls |
Models | Which model runs each AI operation. See Configure custom AI providers with Model Management. |
Augmented actions | The augmented actions available in the Editor, and which ones run on their own. See wxrks Augmented Actions. |
Sous-Chef profiles | Style profiles (domain, audience, formality, tone, creativity and instructions) for the account, Organizational Units and language pairs. See How to set up Sous Chef profiles. |
Automation
Page | What it controls |
Auto Task Placement | Offer tasks to eligible vendors automatically, and decide who counts as eligible. See How to set up Auto Task Placement. |
Task assignment | Whether vendors must accept an offer before work starts, and reminders for tasks close to their due date. See Requiring vendors to accept or reject assigned tasks. |
Due dates | How wxrks calculates project and task due dates. An Organizational Unit uses its own due dates only when every field is filled in. |
Quoting | Projects that quote themselves, and which words a quote counts. See How to use wxrks Quote Automation. |
Notifications | Who wxrks emails and what each email says. See How to customize the email notifications wxrks sends. |
Webhooks | Send events to your systems as they happen. See Webhooks: event notifications. |
Pipelines | Connect events to actions, using the secrets stored here. See Getting started with Pipelines. |
Portal & Routing
Page | What it controls |
Portal | The portal where your clients request translations. See wxrks Translation Portal. |
Project routing | Split one upload into linked projects, one per Organizational Unit and target language. See How to use Project Routing. |
Handshake | Agreements with other wxrks accounts to send and receive work packages. See Send projects between wxrks accounts with Work Packages. |
Finance & Billing
Page | What it controls |
Prices | The price lists used to quote projects. See All about Price Lists. |
Payables | How vendors are paid: which analysis the payment is based on, and coefficient sets per match range and workflow step. See Net Rate Coefficients. |
Taxes | Taxes applied to invoices. See How to configure taxes. |
Company information | Your company details as printed on receivables, payables and the quote report, one template per currency. Business and Enterprise plans. |
Payment integrations | Pay vendors from Payables through PayPal, or keep QuickBooks in sync. Business and Enterprise plans. See How to connect PayPal to wxrks. |
Service providers | Accounts that pay another account's payables with their own payment integrations. |
Settings of an Organizational Unit
Many of these settings can be changed for one Organizational Unit instead of the whole account. Those overrides live on the Organizational Unit's own page, not in Settings. Pages such as Machine translation, Filter settings and Due dates explain on the page how a unit's value relates to the account's. See All about Organizational Units.