At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Page-linked finding | Assign or confirm a remediation owner | Visible correction responsibility | Ownership does not edit the page |
| Content problem | Correct the affected Confluence page | Updated usage | Normal page permissions apply |
| Definition problem | Route the term through review | Governed meaning decision | Only permitted reviewers can approve |
| Corrected source | Rescan the space | New finding state | Prior evidence remains historical |
How it works
- Open the terminology finding.
- Identify the page or definition cause.
- Assign page correction to the content owner.
- Route definition work to a term manager.
- Record the disposition and reason.
- Rescan after the underlying correction.
Example
A procedure uses an unapproved term. The procedure owner removes the premature usage. A term manager continues the definition review separately. The finding records the remediation decision without giving the page owner term-approval authority.
What this does not mean
App ownership does not define employment responsibility or legal accountability. Organizations must map users to real control owners and maintain page permissions separately.
Related questions
Next step
Separate content correction from definition approval in every remediation process.
View on Atlassian Marketplace