At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Authenticated account | Check configured manager role | Allowed or blocked administration | Confluence page access alone is not term-manager access |
| Protected term action | Check role and license | Governed write or error | Inactive licenses block administration |
| Approval action | Check role and actor separation | Independent decision or rejection | Creator, editor, or submitter cannot approve the same content |
| Approved macro read | Return approved visible content | Reader access | No management capability is granted |
How it works
- Open Settings.
- Open Term Managers (RBAC).
- Add the approved manager accounts.
- Save the role configuration.
- Confirm protected actions with a manager account.
- Confirm a normal reader cannot administer terms.
Example
A policy author can edit Confluence pages but is not a term manager. The author can read approved glossary macros. The app blocks governed term administration. A configured manager can create drafts, while a different eligible manager approves them.
What this does not mean
App roles do not define organizational authority, employment duties, or legal qualification. Administrators remain responsible for selecting appropriate managers and reviewing access.
Related questions
Next step
Review the term-manager list before enabling governed workflows.
View on Atlassian Marketplace