Roles
Administration Page | Application/Contract | Syracuse/Collaboration | Class | roles | Representation | role |
---|
A role is an entity describing a particular position or status in a group or organization. For example, a role can be "accounting manager," "sales representative," or "system administrator".
Portal or pages personalized with the personalization tool are usually associated with roles if they have to be shared between several users with the same position in the organization.
The different information entered when defining a role is defined in the following sections:
Defines the code of the role.
Gives a description of the role.
This check box defines if the record is supplied as a factory record. When this happens, a factory code is also displayed and can be entered if you are a factory provider. This features allows to prevent some modifications on records supplied by defaut by Sage or by a vertical solution provider. More information about this feature is given in the following document.
Defines the list of groups a role is associated with. A user belonging to one of these groups will be able to use the role during connection time.
Defines the list of badges a role uses. A badge is an entity supplied by the license provider. For a given installation, a set of badges is provided within the license file. Connecting an user with a given role will consume the badges that are associated to the role. If no more badges are available for the role, the connection with this role will not be possible.
Every badge controls the access to some resources (such as ERP functions). The association between a badge and the resources consumed is defined in a policy file that is also supplied by the license provider. If a resource requested consumes a badge that is not assigned to the role, the resource will not be available.
Associates a security profile that determines the rights of all users belonging to groups where this role applies.
This grid displays the rights a user having this role has on Business Intelligence functionality and reporting that are managed by different Business Objects application servers. Several lines can be added in this grid, but on every line, there must be a different Business Objects application server.
For every Business Objects application server listed here, one of the suitable Business objects profile has to be defined in order to allow the connection to this server.
To connect to a given BO server, a user must have the following rights:
Allows to assign a default navigation page for the current role.
Allows to define the list of landing pages (also called home pages) that are available for the role.
Allows to define the list of mobile applications that are available for the role. If this list is empty, any mobile application will be usable. If at least an application is given, only the applications listed here are available for the role.
This widget presents the links between a role and different entities the role is linked to. The role is represented as a central circle with its name. For more information about the link explorer, see the UI Definition Link Explorer document.