Security at role and user level
Project employees are often composed of varied groups of persons. User departments, company management, IT and many others provide resources across many areas. Project structures are however oriented to established hierarchies, authorities, approval processes and a company's quality assurance and security standards. InLoox bases its response to this situation on a combination of user roles and user accounts. With just the minimum of administrative effort, a flat project organizational structure with clearly defined responsibilities and authorizations can be set up.
Role permissions are defined according to the function carried out by each person involved in the project, be it as project manager, team member, customer, partner or any other activity. InLoox then assigns the correct permission to each person assuming a given role. |
 |
User account oriented permissions apply to all projects. This allows, for example, company management to look at all current and concluded projects, whereas practical responsibility remains in the hands of the project manager and team. |
 |
The InLoox authorization master record is finely structured and freely definable. The system allows the assignment of specific read-only or update permissions, for example to separate those for planning elements from those for the recording of activities or budgeting. |
 |
The permission logic of InLoox is an cumulative process, allowing complex structures to be set up. The inclusion of freelance employees, trainees or suppliers is no problem, since all persons involved are allowed access only to exactly the information that is intended for them. |
 |