Use case: using Groups to manage access to flows
Last updated
Last updated
Imagine a workspace where people from various departments within a company have access to specific modules and workflows. For security reasons, it's crucial that only the members of each department have access to the corresponding data and workflows.
To ensure this, we will use the "Groups" feature. Each department will only have access to the workflows and modules that are relevant to them.
As an example, we will configure access for the Human Resources department, allowing employees to view only the workflows specific to their department. Additionally, there will be a separate group for department leaders.
We will , each with the following characteristics:
Human Resources: Includes all employees from the Human Resources department.
Human Resources Admin: Includes only the department leaders.
After assigning the employees to their respective groups, we will save the changes.
The image below shows the result:
Now it's time to define access to the workflows. In "Integrations," we will click on the Human Resources integration and then click on "Groups." For the integrations, we will select both groups and delete the "Default" group.
However, there is a workflow called "Dismissal medical examination" that we want only the leadership to have access to.
Done! After these configurations, the following views are available:
Human Resources Group: can view two workflows.
Human Resources Admin Group: can view all workflows, including "Dismissal medical examination".
As explained in the documentation, . So, let's click on the three dots of the workflow, select "Groups," and choose the "Human Resources Admin" group.