wxrks treats a Translation Memory match as either a 100% match (the source text is identical) or a stricter 101% match (In-Context Exact match) — the text is identical and the surrounding context matches too. Three settings control exactly when that stricter 101% match is awarded, at both the Account level and the Organizational Unit level: Require Context for 101% Matches, Require Context for 101% Matches (Single Segment), and TM Context Priority. This article covers what each one does, where to change it, and how the Account-level and Organizational Unit-level copies of these settings relate to each other.
​

For the rest of what a Translation Memory does and how it's linked to projects, see All about Translation Memories. For every other Organizational Unit setting, see All about Organizational Units — this article only goes deep on the three TM Context settings that article introduces.

💡 Who is this for? This guide is for Account Admins who need to control how strict Translation Memory context matching is, at the Account level and for individual Organizational Units within the wxrks platform.

A 100% match only compares the segment's text. A 101% match additionally requires context: either the previous/next segment in the file matches too, or the segment carries a matching Context Key (metadata identifying where it comes from — a specific UI string ID or spreadsheet cell, for example). Context makes a match more trustworthy: two identical sentences that appear in completely different parts of a document, or in different documents entirely, might need different translations depending on where they sit — a 101% match confirms the surrounding situation is the same too, not just the wording.
​

The three settings below decide how strictly that context requirement is enforced, and which type of context wxrks checks first. Each one exists twice: once as an Account-wide default, and once per Organizational Unit, which can keep the Account's value or override it independently.

An Account Admin sets the account-wide default from Settings > Account Settings > Usage, near the bottom of the Account Settings section.
​

Changing either Require Context for 101% Matches toggle here asks a follow-up question — apply this to every Organizational Unit in the account too? Confirming overwrites that setting on every existing Organizational Unit immediately; declining only changes the Account's own default, leaving every Organizational Unit's current value untouched.
​

TM Context Priority works differently, and it's easy to miss: changing it at the Account level always pushes the new value to every Organizational Unit right away — there's no option to change only the Account default. Keep this in mind before changing it here if any Organizational Unit is deliberately running a different priority mode.

Each Organizational Unit has its own independent copy of all three settings, under its General tab — click More settings to reveal them alongside the rest of that tab's toggles. See All about Organizational Units for everything else on that tab.
​

A value set here applies only to this Organizational Unit's own projects, and only changes when someone edits it directly on this tab — it doesn't update automatically if the Account-level default changes later (except for the one-time bulk pushes described above, if an Account Admin chooses to apply a change to every Unit). When Require Context for 101% Matches is off for a Unit, its TM Context Priority dropdown stays visible but visually dimmed, with a note underneath confirming it's currently inactive.

Default: enabled. This is the main switch for the stricter match type.
​

Default: disabled. This setting exists for one specific edge case: a file that contains only a single segment — a one-cell spreadsheet, or a single UI string — has no previous or next segment for wxrks to check.
​

When enabled, a single-segment file's segment can only reach a 101% match through a Context Key, since a previous/next-segment check is never available for it. When disabled, the main Require Context for 101% Matches setting still applies as usual — this toggle only tightens the single-segment case further, it doesn't loosen anything on its own.

Default: Context Key First. When both a Context Key and a previous/next-segment match are available for a segment, this setting decides which one wxrks actually checks — or whether it checks both.
​

If the segment can't actually be checked the selected way — for example, Context Key First is selected but the segment has no Context Key at all — wxrks falls back to the default priority order instead of simply failing the match, so the most accurate result is still found.