Rights Hierarchy

Learn about the Aurea CRM's right's hierarchy.

Aurea CRM's rights system operates on multiple levels. Access rights are combined at runtime and are applied in the following order:

• Station access rights apply to all users who log on to the station the access rights are assigned to, see Defining a Station.
  Note: For all Aurea CRM products apart from Aurea CRM win, Station rights are defined in the database of the current station. However, you can also apply the station rights of another station. Create a file $$AS in the \system\sys directory e.g. of Aurea CRM web. If this file contains another station number than that of the current station, the access rights defined for that station apply. This $$AS file created should be in plain text encoded in ASCII or UTF8 without BOM. It must not be encoded in UTF8+BOM as this results in errors.
• Group access rights apply to all members of the (rights) group the access rights are assigned to, see Defining Groups.
• Rep access rights apply to individual reps, see Defining Reps.
• If a rep logs on using one or more roles, the access rights assigned to the login roles are also applied with the priority defined in the login roles, see Login Roles.

You can merge two or more rights formats in a single rights format in order to display or test the combined settings, see Merging Access Rights.

By default, the restrictions defined are cumulative and combined using a logical AND. You cannot remove a restriction defined in station access rights using rep access rights. To partially or completely override the rights hierarchy, you need to inherit access rights, see Inheriting Access Rights.

Rights restrictions are not automatically propagated to child infoareas and elements. The rights in such cases need to be inherited and configured specifically in the inheritance settings. To understand inheritance properties for access rights, see Inheritance Properties per Element. To configure access rights, see Inheritance Settings.