This site has moved to the integrated Appfire documentation and information site for our apps.
From February 2024 this site is no longer updated.
Take a look here! If you have any questions please email support@appfire.com
remove-restriction macro
Overview
The {remove-restriction}
macro is used to remove View or Edit content-level permissions.
Where to use it?
Optional.
One or more {remove-restriction}
macros can be put in a {trigger}
macro.
If you want to add restrictions you can use the {add-restriction}
macro.
You can remove/add or add/remove restrictions using these macros in any order.
If you want to add restrictions immediately after removing restrictions of the same type, you can use the {set-restrictions}
macro instead†.
Restrictions don't give users permissions to content, but rather limit the users who have those permissions.
For example, if everyone has edit/view permissions for the space and you add edit restrictions to a page for user A and user B, only user A and user B can edit the page, and everyone else just view the page.
If you remove restrictions then you simply remove the limits you set for the permission, not the Confluence page permissions.
Parameters
Parameter | Required | Default | Notes |
---|---|---|---|
| What type of permission to remove?
| ||
Note: The permissions are set using Confluence's content-level permissions system and can thus be altered via the padlock icon. | |||
| One or more users to remove
| ||
| One or more user groups to remove
| ||
If neither user or group parameters are defined, then all content-level permissions of type will be removed. | |||
† In some cases, due to Confluence permission threads, rather than using The |
Example
{workflow:Restrictions} {state:Review|approved=Published} {approval:Review} {state} {state:Published} {state} {trigger:pageapproved|approval=Review} {remove-restriction:type=view} {remove-restriction:type=edit} {trigger} {workflow}
All examples
See also
External Links: