This guide explains the functionality of roles and how they can be used.
Roles can be used to limit user rights based on specific targets and tools. A role functions as a higher level than access rights. For instance, if a user is restricted to certain tools via a role, the user will only see tasks and documents generated by those tools, regardless of their other access rights. For example, if a user is assigned the "Quality Observations" tool through a role, they will only see documents generated by the "Quality Observations" tool.
Multiple roles can be assigned to a user if they need to view documents or tasks beyond "Quality Observations." Roles do not affect the tools available to the user but only the documents and tasks shown to them.
Usage Examples:
Case: Quality Team
A company has a dedicated quality team responsible for monitoring and handling quality observations. The company creates a "Quality Team" role and grants users document and task rights at specific levels. The tool can also be limited to, for example, "Quality Observations," meaning that members of the quality team can only view and manage tasks and documents generated from the "Quality Observations" tool.
Case: HR
An accident occurs within the company, and an employee submits an accident report. The HR team has an "HR" role, with task and document rights for the entire company, as well as a tool restriction for "Accident Reports." The HR team can view the accident report submitted by the employee, regardless of the target, and can review the resulting document and manage the associated tasks.