Configuring the Spell Check Exception
Overview
The Spell Check Exception allows you to specify terms that should not be flagged as spelling errors. Before you can add exception terms, the feature must be enabled in your account settings.
How to Enable the Spell Check Exception
Access the Context tab, available at both the Organizational Unit and Project levels in Bureau Works.
Locate the Spell Check Exception option.
Toggle the feature to enable it.
Organizational Unit
Project
Adding, Deleting, and Editing Terms Manually
Once the Spell Check Exception feature is enabled, you can manage exception terms as follows:
To Add a Term Manually
In the Context tab, go to the Spell Check Exception List section.
Click Add New Term.
Select the target language for which the term(s) should be added.
In the input field, enter one or more terms you wish to add, separating multiple terms with commas.
Choose whether each term should be case sensitive by checking or unchecking the case sensitivity option.
Click Add Term to save the terms to the list.
To Edit a Term
In the Spell Check Exception List section, locate the term you want to edit.
Click the Edit (pencil) icon next to the term.
Update the term as needed and confirm the change by clicking Edit Term.
To Delete a Term
In the Spell Check Exception List section, locate the term you wish to delete.
Click the Delete (trash) icon next to the term.
Confirm the deletion.
Add a Term Directly from Spell Check Suggestions in the Editor
When working in the Editor, if a word is underlined by the spell check, hover over the term.
A suggestion menu will appear.
Click on the option Add to Spell Check Exception List.
Add a Term From the QA Check Issue List
During the QA Check phase, open the list of spelling issues or warnings.
Find the term you want to add as an exception.
Click on the 3 points option and Add to Spell Check Exception List directly from the warning.
How Inheritance Works for Exception Terms
Terms registered manually at the Organizational Unit level are automatically inherited by all projects created based on that Unit. This ensures that any standard or organization-wide exceptions are consistently applied across all related projects.
Terms registered manually at the Project level, or added directly from the Editor, are stored only for that specific project. These terms are not inherited by the Organizational Unit or by other projects, and will not be visible in the Exception List at the Unit level.
⚠️ Please note For vendor users, the Spell Check Exception feature is disabled by default. As an account administrator, you must enable this feature by updating the user’s permissions. If vendors report that they cannot see this option, please review their permissions and activate the Spell Check Exception List as necessary.