# 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="<https://www.youtube.com/watch?v=JtdX7TKj4Pk>" %}

***

### Access Permissions

In this section you define **who will be able to view and use the segment**.

**Important rule:**\
If the fields **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 setting **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 setting allows the segment to be populated **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**

In this way, each team works only with **the leads that are part of their operation**, keeping the CRM organized.


---

# Agent Instructions: 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:

```
GET https://docs.sprinthub.com/en/topics/relate/segments/segments-permission-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
