Preconditions for roles in the publish flow
Preconditions by different roles in Naviga ID
Last updated
Preconditions by different roles in Naviga ID
Last updated
The Naviga Writer is configured with Naviga ID so that the publish flow can be managed with the following roles.
Role | Config |
writer:admin | writer:group/admin |
writer:approver | writer:group/approver |
writer.author | writer:group/author |
writer:contributor | writer:group/contributor |
writer:editor | writer:group/editor |
writer:external | writer:group/external |
writer:powerUser | writer:group/powerUser |
writer:readOnly | writer:access |
writer:group/readOnly | |
writer:user | writer:group/user |
That means that you can have different roles that can have permissions to do certain parts in the publish flow. In the Writer view it can look like this with an approval workflow.
For example maybe only an Approver or Editor should be able to Approve and from the approved-state be able to Publish and that is then set up as Permission in Preconditions for the nextState. See the config example below.
The full Publish flow then can be described in four steps.
As described in the release notes for Writer 6.0.0 (Configuring Extended Publishing Statuses) an example from the config code looks like this:
The plugin configuration for a draft->review->publish
workflow where only administrators are allowed to go from approal state: Review
to publish
. The administrators are only an example, you can set any of the above roles suitable for your workflow.
The config above describes that a user can save to the review status, but not go from the review status to publish. The preCondition.permissions
in the block below shows that only users in the admin groups are allowed to publish an article.
"imext:review" is a custom publishing status which is supported with the release of EditorService 5.0.0
.
The custom publishing statuses are further described in the Default configuration definitions.