RestrictPulse for Confluence

Bulk page restrictions · edit inheritance · restrictions report · by PuzariCloud

Confluence Cloud makes you change restrictions page by page, and child pages never inherit edit restrictions. RestrictPulse changes restrictions on a whole page tree with a preview and undo, makes new pages inherit their parent's edit restrictions, and shows who can see and edit what.

Bulk restrictions

  1. Open a page, click ••• → Apps → Bulk restrictions (RestrictPulse).
  2. Choose an action: add people or groups, remove them, replace a person or group with another, copy this page's restrictions to the pages below, make edit restrictions inherit down the tree, or remove restrictions.
  3. Choose View, Edit or both, and which pages: this page, this page and all below, or only the pages below.
  4. Click Preview changes. Every page is listed with its current view and edit restrictions and the exact change. Untick a page to leave it and everything below it alone.
  5. Click Apply. Each page shows Done, Unchanged or the reason it failed. Undo this run puts every page back.

Changes run with your own Confluence permissions: you can only change pages where Confluence lets you change restrictions. A page that someone changed after your preview is left alone; preview again to include it. Confluence requires you to stay in any restriction you create, so RestrictPulse adds you where a new restriction is created (the preview shows it).

Inherit edit restrictions automatically

Confluence passes view restrictions down to child pages, but not edit restrictions. Turn on a rule for a parent page, either at the bottom of the Bulk restrictions dialog or in Space settings → Integrations → RestrictPulse → Inheritance rules. From then on, every page created under it, or moved in, gets its parent's edit restrictions within a few seconds.

Rules apply to new and moved pages. To bring existing pages in line, use the bulk action Make edit restrictions inherit down the tree on the parent page. To set the edit restriction on a page, Confluence requires the app to be on it, so automatic changes add "RestrictPulse for Confluence" to the edit restriction. That also lets the rule keep working further down the tree.

Restrictions report

In Space settings → RestrictPulse → Restrictions report, click Scan space. You get every page with view or edit restrictions, and every page hidden by a view restriction on a page above it. Filter by page, person or group, and click Export CSV. Pages you can't see are not listed.

Audit log

Every change is logged: bulk changes, automatic rule changes (with the reason if one failed) and rule changes. Filter by source, export CSV, and undo a bulk run from the log.

Limits. Pages only: folders, whiteboards and databases aren't changed yet, and a page directly under a folder counts as a top-level page. Rules copy edit restrictions only. The preview and report use Confluence search, which can take a few seconds to show very recent changes.

Who can do what

Anyone can open the Bulk restrictions dialog; changes succeed only where Confluence allows that person to change restrictions. Rules, the report and the audit log are for space admins and Confluence admins, checked on every request.

Security and privacy

RestrictPulse runs on Atlassian Forge (Runs on Atlassian). It stores rules and the audit log in your site's Forge storage and makes no calls outside Atlassian. See the privacy policy.

Support

Email support@puzaricloud.in. We reply within one business day.