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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Overview

One or more trigger actions can be set for a named event in the workflow.

When the workflow trigger event occurs the trigger will check that any required conditions are met, and if met the "remove-restrictions" action removes page-level content view and edit restrictions for specified users/groups.

"remove-restrictions"

The trigger action  "remove-restrictions" will remove content view and edit restrictions for all users/groups.

  • action (remove-restrictions
  • contentId (string) The content id of the page to remove page-level restrictions (if missing, the current page id will be used)

A useful instance would be to use this trigger action to remove all view and edit restrictions from the final state in a workflow.

"triggers:"
[
	{"event": "on-change-state",
	"conditions":
	[
		{"final": "true"}
	],
	"actions":
	[
		{"action": "remove-restrictions"}
	]}
]

(info) If adding the JSON trigger using workflow builder there is no need to include the opening "triggers:" JSON markup notation, since It will be added by workflow builder.

Space admins can configure a space workflow in the space tools Document Management dashboard to remove all page level restrictions on transition to the workflow final state.

(warning) Only 'Confluence Cloud Standard, Premium and Enterprise Plans' enable Atlassian Confluence users to edit permissions, including global, space, and page permissions.

  • No labels