> 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/topics/relate/segments/segments-permission-settings.md). # Segments - Permission Settings The **Segment Permission Settings** define **which users or departments can access and use a given segment** within the system. This helps control access to information and better organize data across teams. {% embed url="" %} *** ### Access Permissions In this section you define **who will be able to view and use the segment**. **Important rule:**\ If the fields of **Users** and **Departments** are left blank, **all system users will have access to the segment**. #### Users Allows you to select specific users who will be able to access the segment. Example: * Pamela Pitanga #### Departments Allows access to be granted to all users in a specific department. Example: * Support Thus, all users who belong to the selected department will have access to the segment. *** ### Segment Owner When this option is used, the segment **will show only the leads that belong to or that the owner has access to**. ⚠️ Important:\ This configuration **does not consider the owner's departments**, only the leads directly linked to them. Available options: * **No owner**\ The segment will not be restricted to a specific owner. *** ### Populate only the leads that belong This configuration allows the segment to be filled **only with leads belonging to certain users or departments**. You can select: #### Users Choose specific users whose leads will be included in the segment. #### Departments Select departments so that **only the leads belonging to those departments** be part of the segment. *** ✅ **Practical usage example** * Allow access only for the **Support department** * Populate the segment only with **leads belonging to the sales team** This way, each team works only with **the leads that are part of its operation**, keeping the CRM organized. --- # 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/topics/relate/segments/segments-permission-settings.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.