Versions Compared

Old Version 3

changes.mady.by.user Robert Alexander Marshall

Saved on

compared with

New Version Current

changes.mady.by.user Robert Alexander Marshall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

When the workflow trigger event occurs the trigger checks 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.

Info

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

"remove-restrictions"

Excerpt

The trigger action  "remove-restrictions" removes 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 typical use is to use this trigger action to remove all view and edit restrictions from the final state in a workflow.

Code Block
"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, it is added automatically 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.

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

Trigger actions

Child pages (Children Display)
pageJSON Trigger actions

Related Pages