Define pre-requisite conditions for transitions and triggers

Conditions allow you to specify additional prerequisite requirements for Triggers and some Transitions.

They are a set of optional parameters which can be added to the macros (listed below) to impose additional limits on when the macro will be active.

In addition, due to support for Value References, you can even create your own custom conditions by comparing metadata values.

Basic example


In the example above, only an administrator can review the content.

Compatible Macros

Note: If a macro has a parameter of the same name as a condition, the parameter – and documentation for that parameter on the macro page – takes precedence.






Value Reference

A specific value, of valid type for the value reference.

Does the value of a value reference match the specified value?

Warning: If used in a {trigger} macro that's listening to the pageupdated event, the trigger will not be activated if the referenced value is still being updated.


A comma-separated list of group names

Is the current user a member of one or more of the specified groups?

When applied to the {approval} macro, you can prefix the list (not items in the list) with & (ampersand) to mandate that all users in the groups defined by the list must take part in the content review.


Name of an {approval}

Has an {approval} of the specified name been Approved for this content?

When applied to an {approval} macro in a {state} with multiple {approval} macros, this enables you to create nested approvals. Just make sure the {approval} you are referring to is defined prior to where the condition is used.


A comma-separated list of content labels.

Does the content have one or more of the labels specified?

(info) ischildof

Title of required ancestor page.

Does the current page have a parent or ancestor page of the specified page title?

(info) ishomepage

  • true – Yes, it's the home page
  • false – No, some other page

Is this page set as the space home page?

See also: How to set space home page


  • true – Yes, the change was minor
  • false – No, watchers were notified

Did the content editor uncheck the "Notify watchers" checkbox (indicating a "minor change") before updating the content?

This condition can only be used on the {trigger} macro when listening to the pageupdated or newsupdated events.

(info) isorphan

  • true – Yes, the page is an orphan
  • false – No, the page has a parent page

Is the page an orphan (no parent page)?

(info) parenthaslabel

A comma-separated list of content labels.

Does the parent (or any ancestor pages) have one or more of the labels specified?


  • edit – user can edit the content
  • view – user can view content
  • administer – user can administrate content

Does the user have the specified permission for the content?

See also: Roles and Permissions

† Irrespective of additional view restrictions resulting from Publishing

‡ Additional administrators can be defined via the adminusers parameter on the {workflow} macro.

space or spacekey

A space key.

Is the page or blog post in the space defined by the space key?

Note: The space key is usually shown in URLs, or on the Space ToolsSpace Overview screen.


A {state} name.

Is the workflow for this content currently in the named {state}?


A {state} name.

Is there an unpublished version of this content in the corresponding Draft Space?

Note: This condition requires the Comala Publishing app to be installed.


Content title.

Does the content (page or blog post) have the specified title?


Comma-separated list defining one or more users via their username or user groups.

Is the current user one of the users listed?

Note: You can include anonymous if you want to check for users who are not currently logged in to Confluence.

When applied to the {approval} macro, you can prefix the list (not items in the list) with & (ampersand) to mandate that all users in the groups defined by the list must take part in the content review.
usersdefinedComma-separated list of Value References

Does the value reference define users?

This is useful when using {workflowparameter} macro to create editable value references – you can check to see if the entered values are valid user accounts.


(info) – Denotes conditions which can only be used on pages, not blog posts.

† - Conditions are evaluated as AND conditions, with the exception of user and group. When both conditions are used, it's applied an OR clause i.e., (user or group) either one of those parameters is required for the condition to be true.


Conditions are compared to values. Values can optionally be negated with a ! (pling / exclamation mark) symbol:

{...|condition=value|...} -- value must match
{...|condition=a,b,c|...} -- one or more of the values must match
{...|condition=!value|...} -- value must not match
{...|condition=!a,b,c|...} -- none of the values must match


See also

Workflow Authoring Guide: