Skip to main content

Executing a platform workflow in a multi-org. enabled environment


Executing a platform workflow in a multi-org. enabled environment

Zuora multi-org. supports the following workflow capabilities:

To set up a workflow, you must either be a Platform Administrator or assigned a Platform role that contains at least the Workflow Manage Access permission. 

Follow Manage access permissions for Workflow to view your current Platform Role. 

If you need higher Workflow access, contact an administrator of your tenant for help. 

  • A user with the appropriate permissions can create a workflow for your multi-org. tenant.
  • The created workflow will be visible only to the org unit it is created in. If the workflow is created at a parent node or a branch node, it will be visible to all the org units succeeding it. 
  • A workflow will be executable only in the context of the org unit it is created in. This does not apply to the workflows that are already existing in your tenant at the global or parent level. It applies only progressively to any new workflows that have been created once multi-org is enabled on your tenant.

An example of a workflow in the context of multi-org.

The following image displays all the workflows created at a tenant level:

workflow 1.png


There are a few workflows specific to the United States (a branch-level org unit) and US Midwest (a leaf-level org unit). When a user switches context to the United States which is a branch-level org unit, the workflows specific to other org units are no longer visible, as displayed in the image below.

Workflow 2.png


Upon switching to another leaf-level org unit, for example, US Northeast, the user can only see the workflows created in that org unit. 

Workflow 3.png


The image below represents another example of org switching and a contextual view of the workflows exclusive to the selected org unit. 

Workflow 4.png