🚀 Get to pre-production in weeks, not months, with private training direct from Jube’s developer — real sovereignty, zero vendor lock-in.

Permissions

Permissions grant access to resources in the user interface, typically pages. Permissions are added to Roles, and then a Role is allocated to a user.

In practice, it is unlikely that a user with day to day responsibilities in customer services would require access beyond Case Management, Lists, Dictionary or Override. Similarly, an analyst that has responsibility for the creation of rule and reports is unlikely to need access to those pages enjoyed by customer service.

Most permissions grant access to a page. A small number instead gate a single action that is materially more dangerous than the rest of the page, and are withheld by default. Apply Force Override is one of these: the ordinary Override permission lets an operator mute an Activation Rule for a value, whereas Apply Force Override lets them make one fire, raising response elevations, creating cases and sending notifications. Import Preservation Snapshot is another: the ordinary Preservation permission lets an operator take a snapshot and export, whereas this one lets them roll the whole tenant’s configuration back to an earlier one. Both are granted on upgrade to the Administrator role only, and must be granted explicitly to any other role that needs them.

In the absence of a permission the user will not be able to navigate given absence of the resource in the menu. In the event of deep linking to a resource without a permission, an unauthorised http status code will be returned.

The Administrator role is created during migrations and has all available permissions allocated. To view permissions for the Administrator role, start by navigating Administration » Security » Permissions:

Locate the triangle to bring about an expansion of the tree, to expose the permissions for the Administrator role:

Click to expand permissions for the Administrator role:

Locate the Read Write Case permission for the Administrator:

Click on the Read Write Case permission to expand on the properties:

Deleting this permission will render the Case pages inaccessible:

Locate the Delete button:

Click the Delete button and confirm:

Refreshing the whole page will construct the menu without the Case menu item for absence of permission:

To establish the permission once again navigate to back to Administration » Security » Permissions, and click on the top on the tree node Administrator to create a new entry:

To add a permission is to select the permission from the drop down of available permissions. Locate the permissions drop down:

Select Read Write Case and ensure Active:

Click Add to create a version of the permission:

As permission may not be added twice. In the event the permission has already been allocated to the Role, the existing entry will be updated for the new properties. With the permission resetablished to access the Cases, a refresh of the whole page will make available the menu item: