Direct answer
A controlled vocabulary in Confluence needs approval, version history, usage checks, and clear owners. How regulated teams can manage a controlled vocabulary in Confluence without relying on static glossary pages or spreadsheets. The page is scoped to terminology governance only: approved definitions, review workflow, version history, scanner findings, and CSV evidence where available.
What Compliance Glossary does
Control termsStore regulated terms as records with owners, status, and version history.
Review changesUse draft, review, approved, and deprecated states with four-eyes approval where applicable.
Find driftScan Confluence pages for undefined, deprecated, unapproved, or synonym terminology findings.
Boundary
Compliance Glossary is not a QMS, GRC platform, legal opinion, certification, page-approval system, or audit-management tool. This page covers current product positioning and links back to the canonical product page.
Useful next checks
- Confirm the target team already uses Confluence for the relevant documentation.
- Confirm the same terms recur across more than one page, policy, procedure, or evidence record.
- Confirm who approves definition changes and where that evidence lives today.