> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/how-to/use-case-using-groups-to-manage-access-to-flows.md).
# Use case: using Groups to manage access to flows
### Context
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.
### Step by step
1. We will [create two groups](/english/skyone-studio/overview/settings-and-preferences/users-and-permissions.md#permissoes-1), 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:
Setting up the Human Resources and Human Resources Admin groups
{% hint style="info" %}
All users in a workspace belong to the "default" group, and this group cannot be edited.
{% endhint %}
2. 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.
3. However, there is a workflow called "Dismissal medical examination" that we want only the leadership to have access to.
As explained in the documentation, [workflows follow the hierarchy of integrations](/english/skyone-studio/overview/settings-and-preferences/users-and-permissions.md#key-points). So, let's click on the three dots of the workflow, select "Groups," and choose the "**Human Resources Admin**" group.
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".
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.skyone.cloud/english/skyone-studio/how-to/use-case-using-groups-to-manage-access-to-flows.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.