FieldLogs

The purpose of Publication roles is to tag users. They can be used in lifecycles or in conditions.

For example, in a lifecycle, they indicate the function of users and what action they are responsible of (who can initiate, review, approve or publish the template). Contrary to security roles, lifecycle roles do not have security rules.

There are five predefined roles when you create an enterprise:

These roles are set by default to each step of the lifecycle:

A user with one of these role is responsible for the validation of the corresponding lifecycle step.

For example:

A publication process is initiated on a template by the user with the role Product Manager.

The user who has the role Author receives the publication task and must perform the Edit step. He performs the changes asked in the Initiate step. He validates the Edit step.

The publication task goes to the user who has the role SME Reviewer for the Review step.