Permissions enables you to view the pages that specific roles have permissions to in ebs: ontrack Hub. For example, to view all the pages and permissions available to learners using ebs: ontrack Learner Hub. To use Permissions, you must have the role Manage Ontrack Permissions. For more information, go to ebs: ontrack Permissions.
For each module, that is ebs: ontrack Hub or ebs: ontrack Learner Hub, you can use the filters to search for specific permissions as follows:
- Roles
- Roles that you want to view permissions for. Note that for ebs: ontrack Learner Hub there is only one role available, that is Learner.
- Include context links
- Whether the associated context links for pages, as defined in ontrack Designer, are shown in the search results.
- Include report links
- Whether the associated report links for pages, as defined in ontrack Designer, are shown in the search results.
- Include access denied
- Whether to include pages that the role does not have permission to use. For example, a staff member may not have permissions for Markbook Verification.
You can sort and filter the search results using the column headers such as Context, Screen Name, and so on. For example, to show all the results for a specific context such as Application. The image below shows the permissions for the module ebs: ontrack Learner Hub and role Learner.
On finding the screen of interest you can then choose the page by selecting one of the options in the Page Description drop-down, as shown in the image below. For example, to prevent learners from accessing screens that they do not need access to.
On saving changes, permissions checks to ensure that the screen has not been checked out by another user in Designer.
Designer
Screens cannot be concurrently edited in permissions and Designer. Therefore, if any screens are checked out in Designer whilst the screen is being edited in permissions, on attempting to save the changes made in permissions you will be notified that the changes cannot be saved because of a concurrency conflict.
If a screen is checked out in Designer, before another member of staff uses permissions, the screen cannot be edited in permissions. The image below shows a screen that is locked and cannot be edited in permissions.
Note that changes made in permissions are only shown in Designer after the changes made in permissions are saved and the screen is reopened in Designer.