Skip to main content

Managing the Spell Check Exception List

Set up and maintain the words wxrks' spell checker should ignore, at the Organizational Unit and Project levels, or add them on the fly from the Editor and QA Check.

The Spell Check Exception List lets you stop specific words from being flagged as spelling errors by wxrks' spell checker — brand names, acronyms, or industry terms that a dictionary doesn't recognize. You manage it at the Organizational Unit level, the Project level, or both, and you can add words to it without leaving the Editor or a QA Check.

💡 Who is this for? This guide is for Project Managers and Account Admins who need to set up and maintain the words wxrks' spell checker should ignore within the wxrks platform.


How the Exception List Works

The Exception List exists at two independent levels, each with its own on/off toggle and its own list of terms:

  • Organizational Unit — terms added here are meant to apply to every project under that unit.

  • Project — terms added here apply only to that one project.

⚠️ Important: a project only inherits its Organizational Unit's terms if both toggles are on. If the Organizational Unit's Exception List is Disabled, a project only ever sees its own terms — even when the project's own Exception List is Enabled. Turning the Organizational Unit's toggle off also immediately stops that inheritance for every project under it, including ones where it was previously supplying terms. To get an Organizational Unit's terms flowing into a specific project, turn the toggle on at both levels.

Any word added directly from the Editor or a QA Check (see below) is always saved at the Project level — it never gets added to the Organizational Unit's list.


Enable the Exception List

Open the Context tab — at the Organizational Unit level from Organizations > Organizational Units, or at the Project level from a project's Project Overview page — and scroll to the Spell Check Exception List card. Click the Enabled / Disabled button to turn the feature on. Add New Term stays disabled until the list is enabled.

Organizational Unit level:

Spell Check Exception List card on an Organizational Unit's Context tab, with the Enable/Disable toggle and Add New Term button highlighted

Project level:

Spell Check Exception List card on a Project's Context tab, with the Enable/Disable toggle and Add New Term button highlighted

Add, Edit, and Delete Terms Manually

Add a term

  1. Click Add New Term.

  2. Choose the target Language the term applies to.

  3. In the Term(s) field, enter one or more words, separated by commas.

  4. Toggle Case Sensitive on if the word should only be ignored with that exact capitalization.

  5. Click Add Term.

Add New Term modal with Language, Term(s), and Case Sensitive fields highlighted

The list shows each term's language, a case-sensitivity indicator, and Edit/Delete icons. A project's list additionally shows the source language a term is paired with, since project-level terms can come from any of the project's target languages.

Edit or delete a term

Click the Edit (pencil) icon to change a term's text or case sensitivity, or the Delete (trash) icon to remove it — deleting asks you to confirm first.

Project-level Spell Check Exception List showing a term with its source and target language badges, and the Edit and Delete icons highlighted

Quick-Add From the Editor and QA Check

Once the Project-level list is enabled, you don't have to go back to the Context tab every time — you can add a word the moment you spot it, from two places. Both require the Add Terms to Spell Check Exception List permission (module: Editor), which an Account Admin grants through Permission Groups — without it, a user can still see spelling suggestions but won't see the option to add an exception. Either way, the word is saved to the Project's list, the same as adding it manually there.

From the Editor

When the spell checker underlines a word in the Editor, click into it to open the suggestion popover and click Add to Dictionary — the popover also has its own Case sensitive checkbox. See Spellcheck in the Editor for the full popover walkthrough, including how suggestions, Ignore, and AI-powered grammar/style checks work.

From the QA Check issue list

  1. Run a QA Check and open the issue list.

  2. Find a spelling warning for the word you want to exempt.

  3. Click the (three-dot) menu on that warning and choose Add to Spell Check Exception List.

[SCREENSHOT PLACEHOLDER]


Vendor Access

Enabling the list and managing it from the Context tab is a Project Manager / Account Admin task. A vendor can still use the two quick-add shortcuts above while translating or reviewing, but only if an Account Admin has granted them the Add Terms to Spell Check Exception List permission — it's off by default. If a vendor reports that they can't find Add to Dictionary or Add to Spell Check Exception List, check their Permission Group first.

Did this answer your question?