> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/hablla/settings/permissions.md).

# Permissions

Manage permissions in Hablla: define user and administrator profiles or create custom access to ensure security, organization, and control.

{% embed url="<https://youtu.be/fNwoRtyiGOg?si=GOuzXfiI4-c_rWL6>" %}

## Permissions in Hablla

The **Permissions** define which resources each member of your team can access within Hablla.\
They are essential to ensure **security, organization, and control** over workflows, support requests, and platform settings.

***

### Default permission types

#### 👤 User

* Limited access to the information assigned to them.
* Can view and act only on the support requests and people they are responsible for.
* Ideal for **agents, SDRs, and operational team members**.

#### 👨‍💼 Administrator

* Full access to all Hablla features.
* Can view **all conversations, support requests, people, and organizations**.
* Has access to **settings, workflows, dashboards, and reports**.
* Can **invite new members** to the Workspace.
* Indicated for **managers, team leaders, and environment administrators**.

***

### Custom permissions

In addition to the standard profiles, Hablla allows you to create **custom permission profiles**, adjusting the experience according to your company's needs.

You can define:

* Access to specific modules (e.g., Flows, People, Opportunities).
* Read or edit access in reports.
* Permissions to create, edit, and delete records.
* Limit which departments or teams the user can view.

This flexibility ensures that each collaborator has access only to what they need, avoiding risks and maintaining operational governance.

### Permission level

**User** - The user will only be able to access records they own or follow.

**Department** - The user will have access to records from the departments related in the list below. Each department can have a different access level.

**All** - The user will have access to all records in the workspace.

**User departments** - The user will have access to all records that are in the departments they have access to.<br>

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2F2Y2BCa3fYsWfz0yn1XD8%2Fimage.png?alt=media&amp;token=f1952904-3be8-4f9c-bcca-b1b95882668e" alt=""><figcaption></figcaption></figure>

#### People

In this section, you can adjust the permission at the **people** level according to your business rule.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2F2mnaBpRrFhtnYbLxsimM%2Fimage.png?alt=media&amp;token=d6491ebd-0d9f-48a1-ade2-1a7daf48ffbb" alt=""><figcaption></figcaption></figure>

#### Organizations

In organizations, you can select access permissions at the **Organizations** level that best fit your team's needs.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2FC2Gi8peYcpmBnEYumtPb%2Fimage.png?alt=media&amp;token=c4752438-7ce5-464c-b56e-a4c676d622bc" alt=""><figcaption></figcaption></figure>

#### Support requests

In support requests, you can select access permissions at the **Support requests** level that best meet your team's needs.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2F0w8EGySG57qwVrchs8fA%2Fimage.png?alt=media&amp;token=34dfdac8-b517-4b80-9a0d-cb5ac7a57108" alt=""><figcaption></figcaption></figure>

#### Cards

In the Cards section, you can change access permissions at the **Cards** level in the way that best fits your business rules.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2FDco3xPKp7MlAmcGTF9nB%2Fimage.png?alt=media&amp;token=c4b0ddff-16be-4852-8437-a92be642d7f3" alt=""><figcaption></figcaption></figure>

#### Tasks

Select here the access level that this permission will have at the level of **Tasks**.&#x20;

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2FR81oZ9vuIk49CRwEOddZ%2Fimage.png?alt=media&amp;token=430eafbb-207f-412b-9014-a80361e747bd" alt=""><figcaption></figcaption></figure>

#### Internal Communication

In this section, you can select access permissions for your team's **Internal Communication** area that best meet your needs.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2F6uxNx733GhijwuNJ4ilj%2Fimage.png?alt=media&amp;token=8df6342a-a742-43dd-8a9b-3e596cb6eb2b" alt=""><figcaption></figcaption></figure>

#### Role Permissions

In this section, you can select access permission to some other usability features of your workspace.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2Ff03yqeqfQMn8SB4jNhO0%2Fimage.png?alt=media&amp;token=44813504-0415-4aca-9395-25c0dbcfb608" alt=""><figcaption></figcaption></figure>

### How to assign permissions

1. In the **Settings**, go to the **Team**.
2. Click on the desired user.
3. Select the permission level: **User, Administrator, or Custom**.
4. In the case of custom permission, configure the specific modules and functions.
5. Save to apply.

### Summary

Hablla's permission system ensures:

* **Security**: access control by profile.
* **Organization**: each user sees only what they need.
* **Flexibility**: ability to create custom profiles.

***

📌 **Practical tip**: keep administrators only for strategic profiles. For operational teams, use limited or custom permissions to reduce risks.


---

# 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.hablla.com/hablla-docs-en/hablla/settings/permissions.md?ask=<question>&goal=<endgoal>
```

`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.