Permissions model
ConfluClean is built to respect Confluence's own permissions at every step. It never shows people content they could not already see, and it never lets them act where they lack access.
What regular users can do
- See only what they can access. Users only ever see content in spaces they have permission to view in Confluence. Data is filtered per user when each view loads.
- Act within their access. Quick actions check space access before they run, so a user can only manage content in spaces they can already work in.
What administrators can do
- The Administration area - global settings, schemes, automations, notifications, exclusions, audit log, and integrity checks - is reserved for Confluence site administrators.
- Administrators configure how ConfluClean behaves for the whole instance, but content visibility still follows Confluence permissions.
Why this matters
This model means ConfluClean is safe to roll out widely. Giving someone access to the app does not expose any content they could not already reach in Confluence, and governance actions stay within each person's existing permissions.