Restrict Access to Spelling Exception Lists

The "add as spelling exception" feature used to be called "add to dictionary" in Core Platform versions earlier than 5.4.

In most Acrolinx Integrations, users can add words to one of several spelling exception lists, so that Acrolinx allows the spelling of the word under certain conditions. You can restrict access to these spelling exception lists with a core server property.

There are three types of spelling exception lists available: "Document", "Guidance Profile", and "Language". Each of these options can affect the work of other users, so they should be used carefully.

For example, if a user accidentally adds a misspelled word to the "Guidance Profile" spelling exception list, Acrolinx will no longer highlight that misspelling when other users check using the same Guidance Profile. Similarly, changes to the "Language" list will apply to all users who check content in that language.

Because of this risk, you might like to restrict access to certain spelling exception lists.

To restrict the available spelling exception lists for the "Add as Spelling Exception" feature, follow these steps:

  1. Open the

    To edit from the Dashboard, go to Maintenance > Configuration Properties, then follow the folder structure config > server > bin and click on the file You can then edit the properties directly from the Dashboard.

    Alternatively, you can edit from the configuration directory: %ACROLINX_CONFIGURATION_ROOT%\server\bin\

  2. Add the following property: 


    Include a comma-separated list of spelling exception list names.

    The possible values are:

    • language
    • guidanceProfile
    • document

    For example, to ensure that users can only update the "Document" list, add the property as follows:


    To allow users to update all spelling exception lists, add the property as follows:


    If this property isn’t defined, the default value is guidanceProfile,document, which means that users can't update the "Language" list.

  3. Save your changes and restart the core server.
  4. Ensure that users reopen their integrations to receive the new setting.