Publish process model

The publication of a process model version follows a publication workflow described below.

  • The Admin (or superuser) creates groups of Requesters and groups of Approvers and adds users to these groups.

    • A Requester is a user who may request to publish a process model version.

    • An Approver is a user who needs to approve the publication of a process model version.

  • The Admin (or superuser) assigns an Approver group to each Requester group. (It is possible to assign multiple Approver groups to one Requester group or vice-versa).

  • When a user in a Requester group requests to publish a model, the request must first be approved by a member of a corresponding Approvers group.

A user who is not assigned to a group of Requesters or who is assigned to a group of Requesters that is not related to the user’s group of Approvers is able to publish process model versions without approval.

Define the “Requesters” and “Approvers” groups

To define a relation between a group of “Requesters” and a group of “Approvers”, the Admin or superuser must have an Admin or a Superuser role in Apromore. Then do the following:

  • Open the User Management window, and select the Groups tab

  • Create a group containing the users that will request to publish process models – Requesters

  • Create a group containing the users that will need to approve the process model publications – Approvers


Create the “Requester-Approver” group relation

The Groups relations tab allows us to define relations between a group of requesters and a group of approvers. The tab has three sections:

  • Select user groups: This section lists all the available groups in Apromore. Here, the Admin selects the Requester group.

  • Select approver group: This section lists all the available groups in Apromore. Here, the Admin selects the Approver group.

  • Existing approver groups: This section lists all the existing relations between Requester and Approver groups.

  1. To create a relation, select any number of groups from the list “Select user groups” and one group from the list “Select approver group”;

  2. Use Create new relation button in the top toolbar to create the relation(s);

  1. To delete an existing relation, click the existing relation and use the Remove relation button.



Requester group (hence, a set of users) may be assigned multiple approver groups and vice versa.

Starting a publication approval workflow

  • In Portal, select a model version and click Publish in the right-click (the publication of a process model version can also be triggered from the top bar of the BPMN Editor).



Make sure that your user belongs to at least one Requester group and that such a group is linked to an Approver group.

  • A message will appear with a Select approver dropdown. We must select the user who will approve the publication of the model version. The users displayed in the dropdowns belong to the “Approver” groups associated with the “Requester” groups that the current user belongs to. At least the Level 1 Approver must be selected.


  • Select a Level 1 approver and a Level 2 approver (if needed).

  • Enter notes for the approvers (if required) and click Confirm.


  • The model version is locked. It cannot be edited until a publication decision is recorded.


Approving or rejecting a model publication request

When the requester clicks Confirm, the Level 1 Approver will receive a notification. The notification will have two shortcut buttons:

  1. The “eye” icon button: By clicking it, a new tab will open, displaying the model version to approve for publication.

  2. The “list” icon button: By clicking it, a new window will open, allowing the approver to approve or reject the model publication.


  1. To approve the model publication, Select Approve and write additional notes if required.

  2. To reject the model publication, Select Reject and write additional notes (this is mandatory for rejections).


Publication approval workflow: Level 1 approver approves

If there is only one approver (i.e., only Level 1) and they approve the publication, the model is published, and its public link is provided. If there are two approvers (Level 1 and Level 2) and Level 1 approves the publication,

Then the Level 2 approver will receive a notification and be asked to decide:

  • If the Level 2 approver rejects the publication, the model is unpublished and unlocked (i.e., editable again), regardless of the Level 1 approval

  • If the Level 2 approver approves the publication, the model is published, and its public link is provided. We will be notified about any decision made in the Notification Center.

Publication approval workflow: Level 1 approver rejects

If the Level 1 approver rejects the publication:

  • The model is unpublished

  • The publication approval process is aborted and will need to be retriggered.

  • If a Level 2 approver was assigned, they will not receive a notification.

Publication approval workflow: Model is published

Once the model publication is fully approved, we are notified via the Notification Center.


By clicking the “link” icon/button, the shareable link of the published model version is copied. All users having access to the shareable link can see the model version in the view-only mode.

Publication approval workflow: States

The status of the publication workflow of a model version is indicated via icons in the Portal.

Waiting for publication

When we request the publication of a model, the state of the model version will be changed to Waiting for publication. This is indicated by an hourglass icon Publis009 next to the process model, in the Portal and in the Details section of the model version.


The model version remains in the Waiting for publication until the last approver records a decision.

When clicking the hourglass icon in the Details section, the Abort publication window appears.


By clicking Confirm, the publication process is aborted, and the approvers are notified via the Notification Center.

Published state

When the last approver approves the model publication, the state of the model version is changed to Published. A globe icon Publis011 is displayed next to the model in the Portal and the Details section for the corresponding version.


When clicking the globe icon in the Details section, a pop-up window appears containing the shareable link. This window includes an Unpublish button.

Locked state

When we unpublish a model version, its state is changed to Locked. A lock icon Publis012 is displayed in the Details section next to the corresponding model version.


When clicking the Lock icon in the Details section, an information window appears.


Publication approval process: Publication history

We can also check the publication history of a process model by clicking the History button, either in the decision-making window (for approvers), in the notifications (for requester), or in the state window (for everyone having access to the model).

Publish different model versions

When we have different versions of a model, we can only publish one version at a time. If we want to publish another version of a published model, we receive a warning that the last version will become unpublished.


Click Confirm to publish the new version.

View model history

To enable us keep track of changes to a published model, we can view the model history. The model history displays previous versions of the model and the time they were last updated. We also see the description (if any) of the published model.

To view the model history of a published model, open the model and click the “info” icon.


This displays the model history.


The screenshot shows that version 1.2 is the published version, and versions 1.0 and 1.1 are now unpublished.

We can view any of the previous model versions by double-clicking it.