Remove restrictions

The Remove restrictions action clears every viewer and editor restriction from the page. It has no fields. Drop it onto a state and that state, on entry, will hand the page back to whoever was allowed to see and edit the page before any restriction was applied.

This is one of the two early-phase actions. Along with Set official version, it runs before everything else in the same state’s Actions list, and the late phase only starts once it has finished. The ordering matters because of how it pairs with Add restrictions: putting both on the same state gives you a clean replacement. The early phase wipes whatever was there, then the late phase writes the new viewer and editor lists. Without the wipe, Add restrictions would layer on top of the existing entries, and previous viewers would linger after a state change that was meant to lock the page down to a new audience.

What “all” covers

The action removes the full set: both the view restriction and the edit restriction, every user and every group on each. It does not distinguish between restrictions Aura placed in an earlier state and restrictions a user added by hand through Confluence’s own restriction dialog. Anything currently restricting the page is cleared. If your workflow expects manually applied restrictions to survive a state transition, do not put Remove restrictions on that state.

There is no scope or filter. You cannot remove only view restrictions, only edit restrictions, or only entries matching a particular user or group. If that level of control is what you need, model it through Add restrictions in a later state — it sets a known list rather than subtracting from an unknown one.

Running it on an unrestricted page

The action is idempotent. A page with no restrictions to begin with passes through cleanly: the action records a success in the history timeline and the late phase proceeds. There is no error, no warning, and no need to guard the action behind a condition. This makes it safe to put on every state in a workflow that wants to enforce a fresh restriction set on each transition, even when some of those states are entered from a clean baseline.

Typical placement

The most common shape is a state that locks the page to a specific audience — a review state restricted to reviewers, a published state restricted to a wider readership — pairing Remove restrictions with Add restrictions so the audience swaps cleanly on entry. A state that should open the page back up to everyone uses Remove restrictions on its own; with no Add restrictions to follow, the page returns to space-level permissions.

For how the early and late phases relate, and what happens if an action fails, see the Actions overview.