Restriction Rules for Confluence

Confluence view restrictions pass down a page tree. Edit restrictions don't, and nothing keeps new or moved pages in line. Restriction Rules does, with a preview of who loses access, a week of watching by default before anything changes, and undo for every run.

What it does

• Rules that keep a page tree's restrictions in line as pages are added, moved, copied and restored.
• Put back what people remove: switch it on for a rule, and when someone takes the rule's group off a page, the rule puts it back.
• Watch first: by default a new rule records what it would change for 7 days before it changes anything.
• A preview in plain sentences: "37 people will lose view access to 12 pages."
• One-off bulk changes across a tree, with undo.
• An audit that finds risky pages and suggests a rule for each finding.
• A report for the switch to space roles.
• A panel on every page: which rules cover it, and who can view and edit each page under it.
• An activity log of every rule change, run, undo and pause, and who did it.
• Space admins can run rules in their own spaces, if a Confluence admin allows it.

Safe by design

• "Pause all rules" stops every rule and bulk change, at once. Undo still runs, so you can put things back.
• It never touches restrictions people set by hand, unless you switch that on for a rule.
• It never locks out the admin who makes or runs a change, and never leaves a page with only the app on it.
• Runs on Atlassian. No data leaves Atlassian. It doesn't read page content, and it can't edit it.