> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/common-questions/permissions/department-permissions.md).
# Department Permissions
In this guide, you will learn how to manage the permissions of a specific department, ensuring that users have the correct access to CRM features and contacts. It is worth noting that the logic applied in this example serves as the basis for managing permissions for all other tools on our platform.
Follow the step-by-step instructions below:
## 📌 Contact Permissions
When accessing the contact, it is possible to modify its access permissions. By changing these permissions, you can define which user or department will have access to the selected contact.
## 📌 CRM - Funnels
By going to Settings > Funnel List > Edit Funnel, you can define the users or departments that will have access to the funnel.
## 📌 Users and Data Control
By going to System Settings > Users, you can define whether the department will have access to contacts created or imported by the user.
### Conclusion
Setting up permissions by department is a fundamental step to ensure data security and the organization of workflows in your company. With this control, you ensure that each employee sees only the information relevant to their role, optimizing the use of CRM and protecting the integrity of your contact database.
---
# 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.sprinthub.com/en/common-questions/permissions/department-permissions.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.