Agencies want to define reusable roles , one of which must be assigned to each administrative login (supporter)
Each supporter can be assigned to exactly one role
Roles are defined per agency (not per circle or application-wide)
A role is derifed from a "view level" of either "Circle Administrator", "Agency Administrator" or "Company Administrator" which directly derives how much data is available to the role.
Based on this view level, certain access rights may be given (or stripped away)
E.g: A Company Administrator will nerver be able to access agency data or data residing outside of their designated company, but may be given access to more or less parts of the company profiles and travelers within these.
The support function Administrate Circle is only visible to a Circle administrator.
Field | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Language | Assign the language in which the user interface should appear for a given administrator | ||||||||||
Home Agency | Default Agency for the administrator. Circle administrators are able to change the agency if there are multiple agencies in their circle | ||||||||||
Support Function | |||||||||||
Administrate circle | In addition to the functions of an agency administrator such a user is able to:
This user has full access to the system of the particular circle and can carry out the same functions as umbrella support | ||||||||||
Administrate agencies | In addition to the functions of a company administrator such a user is able to:
| ||||||||||
Administrate companies |
| ||||||||||
Read-only Access | allows only Read-mode (the user can therefore not edit anything in Faces) | ||||||||||
Profile Reminders | It is only visible if the module Profile Reminder has been activated on the agency under System Settings This field indicates if the administrator wants to be informed of any expired profile data of his associated traveller profiles.
|