How does it work
The Publisher application consists of screens that support the user in executing publish actions. The Publisher is role based, meaning that depending on the role a specific user has, this user will be allowed to access specific sections in the Publisher application. The following sections are available:
- Publisher inbox
- Publish and unpublish projects
- Publisher Environments
- Publication History
- Publications Pending
- Publisher Client
- Publisher API
Publisher roles
| Role | Purpose |
|---|---|
| Publisher | The main role to execute publish/unpublish actions. |
| Approver | If the two man rule applies, this role is used to approve or reject a publish/unpublish action. |
| Investigator | This role is used to view the entire history of publish actions. |
| PublisherAdministrator | This is the superuser role which has all the privileges the other roles have. Note that this role can be used to overrule the two man rule, as it can even approve its own publish actions. |
Each role maps to the sections that it can access in the Publisher.
| Section | Publisher | Approver | Investigator | PublisherAdministrator |
|---|---|---|---|---|
| Inbox | x | x | x | |
| Publish/unpublish project | x | x | ||
| Environments | x | x | ||
| History | x | x | ||
| Pending | x | x | ||
| Logout | x | x | x | x |
Overview
Content Tools