At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Approved term with configured synonyms | Include synonyms in the effective glossary | Preferred-term rule | Unconfigured variants cannot be matched as known synonyms |
| Page content | Compare observed wording | Page-linked synonym finding | Context still needs human review |
| Finding disposition | Record decision and reason | Explainable remediation evidence | Disposition does not change page text |
| Corrected page | Run a new scan | Updated finding state | Prior scan evidence remains historical |
How it works
- Add the known synonym to the governed term.
- Approve the term through normal review.
- Open Compliance Scanner.
- Select the space and Scan Space.
- Review synonym findings and preferred terms.
- Correct the page, record the reason, and rescan.
Example
The approved term is “service interruption,” while several pages use the configured synonym “outage event.” The scanner links those pages to the preferred wording. Owners review context, update controlled content where required, and rescan.
What this does not mean
Synonym matching depends on configured governed data. It does not understand every linguistic variation or decide whether a local exception is justified. Human review remains required.
Related questions
Next step
Configure known variants before using the scanner to enforce preferred wording.
View on Atlassian Marketplace