For each previously added agent, two 'Roles' tabs are available to define and grant permissions and access for that Agent to LUCS elements of LUCS.

All roles shown here are not to be mixed up with Agent traits or responsibilities, and thus also play no role in daily task distribution.

(question) About the Role names: Terms for roles like "Agent" or "User" are just identifiers for the permission tables, used for the permissions matrix of the role based access table.

(lightbulb) The screenshot below shows an example of organization units and how they can be used to inherit roles. However you may freely grant or revoke these rights as you see fit.

Agent Administration Role

Assigning agent roles

  1. Within either the Administration or Agent / Supervisor Tabs. Organization Units (OU) row, select the permissions column you want to grant
    1. Note that clicking a parent OU the child automatically inherit the role
  2. Ensure to press "Save and Apply" to make changes take effect.
  3. Repeat these steps for the Administration and Agent / Supervisor tabs as needed. 


Good to know

  • The grouping by Administrator, Supervisor and Agent allows definitions of very flexible user roles, e.g.: that user may act as Administrator one area while having only basic read and access rights on other areas.
  • Users which are part of "System Administrator" group (defined during LUCS installation) may overrule the roles given in this matrix. They are treated identically as "System" level administrator roles within LUCS with full rights to all organization units. 
  • System-level privileges and Data Privacy rights may only be granted highest level to avoid manipulation of user data and critical structures on a lower level.