Direct answer
ApprovalFlow for Confluence (Flowdence) is a page-approval app: it binds approval to page versions with an approval queue, analytics, an audit trail, and recertification. Compliance Glossary is a terminology governance app: it binds approval to term definitions and scanner evidence across pages. If the risk is "was this page approved in this version", ApprovalFlow answers it. If the risk is "are the controlled terms used across our pages defined, approved, and current", that is the job Compliance Glossary is built for. Regulated teams may need both when they must govern page approvals and controlled terminology.
Feature comparison
| Capability | Compliance Glossary | ApprovalFlow for Confluence |
|---|---|---|
| Runs on Atlassian Confluence Cloud | Yes | Yes |
| Version-aware page approvals | No | Yes |
| Approval queue and recertification for pages | No | Yes |
| Page-approval analytics and audit trail | No | Yes |
| Controlled term lifecycle (draft, review, approved, deprecated) | Yes | No term-level equivalent found in current public docs |
| Four-eyes approval for definition changes | Yes | No term-level equivalent found in current public docs |
| Term version history with change reasons | Yes | No term-level equivalent found in current public docs |
| Scanner for undefined-term candidates, unapproved, or deprecated terms on pages | Yes | No term-level equivalent found in current public docs |
| CSV import and term-level CSV evidence export for audit review | Yes | No term-level equivalent found in current public docs |
| Cross-space term sharing | Yes | No term-level equivalent found in current public docs |
| Inline term highlighting and definition popups | Partial: approved-term macro, no automatic page-wide highlighter | No term-level equivalent found in current public docs |
Where ApprovalFlow is stronger
Where Compliance Glossary is stronger
Boundary
ApprovalFlow capabilities are summarized from the public Marketplace listing and vendor documentation, which change over time; verify current features on the ApprovalFlow for Confluence Marketplace listing before a purchase decision. Compliance Glossary is not a page-approval system: it does not manage page sign-off, queues, or recertification, so the two products are complementary rather than interchangeable.
Useful next checks
- Decide whether the glossary is a convenience or a controlled record with audit consequences.
- Confirm who approves definition changes today and where that evidence lives.
- Confirm whether the same terms recur across more than one page, policy, procedure, or evidence record.
Common questions
What is the difference between ApprovalFlow for Confluence and Compliance Glossary?
ApprovalFlow for Confluence provides version-aware page approvals with queues, analytics, and recertification. Compliance Glossary governs controlled term definitions in Confluence: approval evidence, version history, page scanning for terminology findings, and CSV evidence export.
Can ApprovalFlow for Confluence and Compliance Glossary be used together?
Yes. ApprovalFlow for Confluence covers version-aware page approvals with queues, analytics, and recertification; Compliance Glossary adds term-level governance for the regulated vocabulary used across those pages and documents.
Does Compliance Glossary replace a QMS, GRC platform, or audit tool?
No. Compliance Glossary covers terminology governance only: approved definitions, review workflow, version history, scanner findings, and CSV evidence export.