Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Create and manage roles

Roles and authorisations are managed in the Master Data dialogue Roles. The role concept implemented in the GTC allows a differentiated control over the data access. This concept supports the four-eye principle for the data quality assurance. All available roles are listed in the dialogue overview.
A role is the combination of several authorisations – initially without certain assignment to companies. The authorisations created in the Roles dialogue can be assigned in the User dialogue.
Name [ Unable to render embedded object: File (worddav75885e27e924d844222af95456b48ec1.png) not found. ]
After clicking on the [ ] button, a subdialogue opens, here you can enter the name for the new role. The roll name is freely selectable and can be changed at a later date.

Figure 20: Create a new role
The ID is assigned automatically by the GTC.
Authorisations [Object-Value]
When the role is created, authorizations can be assigned. For this purpose, use the available drop-down menu. The selection list shows all possible combinations of objects [e.g. Master Data] and values [Read, Edit].

Figure 21: Assign authorisations to the created role
An overview of the possible object-values and the associated authorizations or properties can be requested from AMANA. The plus symbol allows you to assign multiple authorisations to a role.
Cascading
If the Cascading checkbox is activated, the selected authorisation is assigned cascading [attribute is thus only relevant for the company-specific authorisations]. For example, if the user is assigned the right to edit the balance sheet comparison for the parent company in the User dialogue, this authorisation also applies to subordinate companies. Such situation is typical for a subgroup: the subgroup manager does not need to have a separate role for each subgroup company. The role must only be assigned to the parent company and then cascaded for all subordinate companies.

  • No labels