Skip to main content
ZenHub houses documentation to support you if you’re using Contensis Classic. Contensis Classic includes our WYSIWYG and templating features. If you’re working with a newer version of Contensis, is your go-to place to find anything Contensis-related when building with content types.

Assign and remove role permissions

A role is made up of a permissions, users and groups and in some cases API keys.

Permissions are actions a user can carry out on a particular resource.

Users and groups define those users who can carry out the actions, either by individual assignment or by being a member of a group.

API keys can be assigned to a role to grant programmatic access to content through the Management API.

Add a permission

With a role open for editing:

  1. Press on the Add permission button. A new permission will be added to the list.
  2. The permission you've added will be active  and the Entry permissions panel will be displayed.

Configure the permission

With a permission selected, the permissions panel will be displayed allowing you to configure which resource the permission relates to.

A resource determines the permissions that are available. Content types are the only supported resource in this release.

  1. Select a content type from the drop down in the Entry permissions panel. A list of available actions that are permissible will displayed. The list of actions depends on the workflow type assigned to the content type.
  2. Use the toggle buttons next to each action to turn entry permissions on or off. As permissions are added, they will appear in the permissions list.
  3. Once you are happy with the permissions, press Save.

If you are providing access to multiple resources, add another permission and configure as per these steps.

Note: Resist any temptation to make a one-off change for a user with unusual needs. If you begin doing this, the role permission system will quickly begin to unravel. Change the roles as required, or add new ones when really necessary.

Common permission events

  • View — the user can view content. The view permission is inherently set when any other permission is granted.
  • Create / save — the user can create new content, and save changes to exisiting content.
  • Submit / revoke — the user can submit and revoke content from review.
  • Approve / decline — the user can approve or decline content for publication.
  • Publish - the user can publish the content for immediate publication.
  • Unpublish - the user can unpublish the content.
  • Delete — the user can delete content permanently.

Permissions are explicitly set, meaning it is possible to setup a role with a permission that depends on another permission to work correctly. This may seem counter intuitive but ensures that access is not given by mistake. An example of this, would be a role, that could revoke an entry but not create / update an entry.

Remove a permission

If you don't need a permission within a role it can be removed:

  1. Locate the permission in the role that you want to remove. 
  2. Press the cross on the permission to remove it from the role.
  3. Press Save to confirm your changes.

Note: Removing permissions from a role will affect any  users or API keys that are assigned to the role.