Restrict access to the Spell Checker feature

In CCMS Web and CCMS Desktop, you can limit access to the Spell Checker feature to only certain users or roles that have appropriate access rights.

To restrict access to the Spell Checker feature:

  1. Edit the accessrights.xml file by taking the following actions:
    1. Expand the Content Store's Repository node and browse to /system/conf.
    2. Right-click accessrights.xml and select Check Out from the pop-up menu.
    3. Open the file in an XML editor.
  2. Go to the last default general UI method, RevertTo, and then add a new method for the Spell Checker feature, using the provided codeblock.
    <method name="Spellcheck" type="front-end">
      <notify enabled="false"/>
        <conditionset operator="any">
          <condition>
            <current>
              <type name="map">
                <statuses>
                  <status>Authoring:*</status>
                </statuses>
              </type>
              <type name="topic">
                <statuses>
                  <status>Authoring:*</status>
                </statuses>
              </type>
             </current>
               <users>
                 <roles>
                 </roles>
                 <groups>
                 </groups>
              </users>
        </condition>
      </conditionset>
    </method>
  3. Specify the roles and groups with access rights by choosing one of the following actions:
    • To disable the feature entirely, leave the <roles> and <groups> elements empty.
    • To restrict access, add only the specific <roles> and <groups>, such as <role name="Writer"/> or <group name="ProductA"/>, based on the valid roles and groups for your configuration
  4. Save your updates, close the file, and check in the accessrights.xml file, and then refresh your CCMS Web instance.
  5. Confirm the update works as you expect, using both a test map and a test topic that Is in the Authoring cycle, but does not have an Authoring:done status.
    Note: The Spell Checker feature will find errors in objects with an Authoring:done status, but it cannot make any updates to it, since such objects no longer allow for edits.