The page Scope

The purpose of this scope is to control access to the various pages of the product's graphical user interface.

Actions of the page domain

Name	Description
view	This is the only possible action on pages. The control is done only to the pages, not affecting access to the resources expended by each of the pages. This implies that it is possible to allow a user to view a page but for the page not to function correctly because the user does not have all the privileges necessary for the page to function.

Specific entities and possible filters of the page domain

Entities:

Name	Description
dashboard.html	Page where you can view the performance data of the application. To work properly it additionally needs the jobreqs:read permission (see below).
cpes.html	Page where you can search for existing devices and act on them. To work properly you also need one or more permissions of the equips scope (see below).
jobs.html	Page where it is possible to view the log of all the interactions (jobs) with the devices. To work properly it needs the jobreqs:read permission (see below).
templates.html	Page where you can manage templates. To work properly you additionally need one or more permissions of the templates scope (see below).
reports.html	Page where you can view the log of all interactions (jobs) with the devices. To work properly you additionally need the reports:read' permission (see below).

Entities (deprecated - to be deleted):

Name	Description
logout.html	Permission for the application to redirect the user to the CPE page after authentication on the home page. For now it will be necessary to add this permission to get this behavior but in the future it will no longer be necessary.
index.html	Permission to see the logout action in the main menu. For now you will need to add this permission to all profiles, but in the future it will no longer be necessary.

Filters:

Name	Description
page_name	Example: (page_name=cob*.html ).