An Organizational Unit is where most of a project's defaults live in wxrks — source and target languages, pricing, billing details, translation behavior, connected Translation Memories and Glossaries, and more. Every new project inherits its starting configuration from the Organizational Unit it's created under, so setting a Unit up well means less to configure by hand on every project after it. This article walks tab by tab through every setting on an Organizational Unit's page.
​

💡 Who is this for? This guide is for Account Admins who need to configure any tab of an Organizational Unit's settings within the wxrks platform.

This article assumes the Organizational Unit already exists. If you haven't created one yet, see How to create an Organization or Organizational Unit first — the Unit's parent Organization and a few other creation-time details can't be changed afterward.
​

Open an existing Unit from Organizations > Organizational Units in the left sidebar, then click into the one you want to configure. Its settings are organized into the tabs below, in the order they appear on screen.

The General tab holds the Unit's identifying details and a set of behavior toggles that become the default for every project created under it — most can still be changed on an individual project afterward.
​

Name, Organization, and Timezone are required. Name is the Unit's own label. Organization is its parent in the account hierarchy, set when the Unit is created and not changeable afterward. Timezone aligns delivery dates for users working across different regions.
​

Memorandum, Tags, Country, and Contact Notes are optional — wxrks doesn't require a Unit to represent a company with a physical address, so most General-tab fields exist to help you organize and search rather than to be mandatory. Tags group and locate Units and their projects, and can also help match a project to vendors with matching specialties. Contact Notes keeps quick reference details visible on the Unit's own page.

Click More settings to reveal the rest of the tab — a long list of toggles plus address and payment-note fields:
​

Below the toggles, Street, Number, Postal Code, City, State, Phone, Mobile, and Website capture the Unit's physical address details, and Payment Notes is a free-text field for banking or invoicing notes (for example, bank and account numbers) that can be referenced during billing.
​

It isn't possible to change an Organizational Unit's foundational creation details, such as its parent Organization — wxrks doesn't support moving these data elements between parents, to protect user data and support SOC 2 Type 2 compliance. An Organizational Unit also can't be deleted from the interface once created.

The Project tab sets defaults that carry over into every new project created under this Unit — source/target languages, tag-capture rules, and a few advanced integration settings.
​

Contact Person and Project Manager set the default point of contact and the default Project Manager for new projects under this Unit. Source Language and Target Languages set the default language pair(s) — both can still be changed by hand on an individual project.
​

Regular Expression defines which parts of your content should stay accessible for translation versus be converted into non-editable tags; turning on Override Default Regex makes this Unit's expression take precedence over the global default. Continuous Tags sets the tags applied to projects created automatically through a connector.
​

Count 100% TM Match Over Repetition and Ignore Subsequent Non-Translatable(s) as Repetitions change how repetitions are counted in this Unit's projects' Logfiles — see All about Logfiles for how the match-tier breakdown works and how these two toggles affect it.
​

Four collapsible panels round out the tab: Continuous Project Configuration (standardizes file-naming prefixes/suffixes for continuous/connector projects), Filter Settings (custom file-parsing filters for new projects under this Unit — see How to customize file parameters), Credentials for Web Preview (credentials used to access the web preview in the Editor), and Update Region for Data Transformation (the processing region used for this Unit's data transformation).

The Prices tab controls which price list(s) apply to projects under this Unit.
​

Currency sets the Unit's default currency, and Show Requester Name displays the client's name on the invoice after a project is delivered. The Prices table lists every price list linked to this Unit, with its currency, minimum-fee basis, default price per word, default minimum fee, and whether it's the Unit's Default price list for new projects. Use Add to link another price list, or Delete to unlink one — a price list must first be linked to this Unit's parent Organization before it can be added here.
​

For how a price list's own fields and minimum-fee rules work, see How to create a Price List.

The Billing tab controls how and when projects under this Unit get invoiced, and holds the recipient details that appear on those invoices.
​

Auto Billing automatically sends an invoice to the billing contact once a project qualifies. Send Invoice to Requester sends it to the project's requester instead of the billing contact. Send Email Notification emails the billing contact whenever a new invoice is created. Require Purchase Order requires a PO number before a project can be approved. Consolidate Invoice combines multiple projects into one invoice when more than one is being billed together. Use User's Account Info lets a manually-created receivable use the logged-in user's own account details instead of this Unit's defaults.
​

Billing Contact and Invoicing Type (Weekly, Bi-weekly, Monthly, Quarterly, or By Project) are required; Payment Method, Acc. Code, Tax ID, Tracking Category (Company), Tracking Category (Type), and Number of Days Until Payment is Due round out the recipient and accounting details, along with Billing Emails and free-text Invoice Information. If your account connects to an accounting platform such as Xero or QuickBooks, additional ID fields here (Xero ID, QuickBooks Customer ID, QuickBooks Product/Service ID) map this Unit's billing records to the matching customer or item in that system.
​

Issue NFe, Simples Nacional, Retain IRRF, and Municipal Registration apply to Brazilian tax requirements only. Quote Notes adds a standard title/description note to every quote document for this Unit's projects, and Taxes lets you attach one or more fixed or percentage-based tax lines to invoices.
​

For how invoices, payables, and the Ready to Invoice queue work once billing is configured, see How to manage the Finance Section.

The Access Management tab controls which users can see and work in this Organizational Unit.
​

The Access Management panel lists every user associated with this Unit. Search for a user and click the + button to add them, or use the delete icon on their row to remove the association.
​

The Portal Access Management panel manages a separate list: portal contacts who use this Unit as their portal Default for Sous Chef Agents, Paid Reviews, and other common settings that a portal user needs a default scope for. Add a contact the same way, by searching and clicking +.
​

For how to create the users you'll add here, see People > Users in the main sidebar.

The Translation Settings tab is a template: every new project under this Unit copies these settings as its own starting point, and can then be changed independently per project. Changing this template later only affects projects created afterward — it never retroactively changes an existing project. For the same settings explained from a project's own point of view, see Project's Translation Settings, which covers each toggle's effect in depth; this section only covers what's specific to configuring the default at the Unit level.
​

Two groups of settings live only here, at the Unit level — they don't appear on a project's own Translation Settings tab, and only take effect at the moment a project is created:
​

A Sous Chef Agent selector on the right sets this Unit's default AI agent for Context Sensitive translation — every project under this Unit inherits it unless the project sets its own. See Sous Chef Agents for how agents cascade between account, Unit, and project.

A project can only use a Translation Memory, Glossary, or the Spell Check Exception list if it's connected here first, at the Organizational Unit level. The Context tab lists all three together.
​

Use Add to link a Translation Memory that belongs to this Unit's parent Organization, and Delete to unlink one. Each linked TM shows its Default, Read, and Write toggles and its Threshold — these become that TM's starting settings for every new project in this Unit. For what these settings mean and how a TM is created and managed, see All about Translation Memories.

Works the same way as Translation Memories: Add links a Glossary that belongs to this Unit's Organization, and each linked Glossary gets its own Default toggle for new projects. See How to create a Glossary for creating and managing Glossaries themselves.

Terms added here are meant to apply to every project under this Unit — but only if the project's own Spell Check Exception List is also enabled. See Managing the Spell Check Exception List for exactly how Unit-level and project-level terms interact, and how to add, edit, or remove a term.

The Net Rate tab controls how vendor payments are calculated for projects under this Unit — which logfile type is used, whether payment is by word count or by hours, and which coefficients weight each Translation Memory match tier.
​

Edit Coefficients lets you select a specific coefficient set for this Unit instead of the account default (recommended if you're unsure). Payment Type chooses between Pre-analysis (a logfile generated before translation, estimating effort) and Post-analysis (generated after the work is done, based on the actual editing distance from the pre-analysis draft) — see All about Logfiles for the full breakdown of what a logfile counts.
​

Pay By chooses whether vendors are paid by Words (using the Net Rate word count from the post-analysis logfile) or by Hours (vendor-reported time, approved by the Project Manager). Count Words From chooses whether word counts come from the source or target content. Quoting Type applies the same Source/Target choice to how project costs are calculated — calculating from Target content requires the project to be pre-translated first.
​

Only an Account Admin can see and change this tab.

The MT tab chooses which connected Machine Translation provider this Unit's projects use, either as a single default or per language pair.
​

MT Settings by default sets this Unit's fallback provider. MT Settings by language pair, added with Add Lang Pair, overrides that default for a specific source/target combination. wxrks checks for a language-pair match first, then this Unit's default, and finally the account's own default if neither is set — see Connect a Machine Translation (MT) Provider to wxrks for connecting a provider in the first place and the full priority order across Account, Organization, and Organizational Unit.

The Segmentation tab lets you upload custom segmentation rule files that change how the wxrks Editor splits a file's content into segments for this Unit's projects. See All about Segmentation Rules for what a segmentation rule (.SRX) file is and how the Account-level vs. Unit-level precedence works.
​

Click Add new segmentation file to upload a rule file for this Unit. If you're unsure how to build one or want help deciding the best approach for your content, contact [email protected] or search the wxrks Community.

The LLM tab controls this Unit's access to wxrks' AI-powered Augmented Actions.
​

Enable Augmented Translation Actions turns Context Sensitive translation and the rest of the Augmented Actions on for this Unit — it only takes effect if the Account itself already has Augmented Actions enabled; a Unit can turn the feature off for itself, but can't turn it on if the Account hasn't. Enable Sending Learned Terms To Terminology Board lets terms the AI learns while translating this Unit's projects be sent to the account's Terminology Board, and likewise depends on the Account owning this Unit having that capability enabled.
​

See wxrks Augmented Actions for everything these toggles unlock, and where the Account-level and per-user Editor settings that also gate this feature live.

The Workflows tab shows this Unit's own workflow overrides and recommendation rule sets, layered on top of the account-wide workflow steps configured in Settings.
​

The Workflows Settings panel is where a Unit-specific override (such as Zen Mode for one workflow step) would appear, if one has been configured for this Unit — it shows Workflows not found when none has. The Recommendations panel manages this Unit's own rule sets for suggesting a workflow based on an uploaded file's extension; click New rule set to create one. When a Unit has an active rule set, it takes priority over the account's own rule set for projects created here. See Managing Your Custom Workflows for the full picture of how account and Unit-level workflow configuration fit together, including how to build a rule set.

The Notifications tab controls which email notifications go out for projects under this Unit.
​

The Attachments tab lets you upload and manage general reference files against this Organizational Unit's own record — for example a signed agreement or a style guide you want kept alongside the Unit itself, rather than any one project.
​

Click Add attachment to upload a file.

The Custom Fields tab shows any custom metadata fields your Account Admin has created for the Organizational Unit entity, letting you fill in a value for each on this specific Unit. Custom Fields are created once at the account level and applied to whichever entities they're associated with — for the Organizational Unit entity specifically, a newly created field is applied to every existing Unit immediately, not just to ones created afterward. See All About Custom Fields for how to create one, which of the other entity types do and don't backfill this way, and how each data type (Boolean, Numeric, Multivalue, Free Text) behaves.