> For the complete documentation index, see [llms.txt](https://docs.echevarrisports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.echevarrisports.com/guia/en/getting-started/roles-y-permisos.md).

# Roles and permissions

Everyone in the CRM has one of these three roles. Direction assigns it in **Team › Access**.

| Role                  | What they can do                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------- |
| **Direction**         | Everything: P\&L, margins, pay profiles, salaries, rates and each coach's economics.                    |
| **Financial Control** | Cash received, VAT, the accountant export and the monthly payroll. No P\&L, margins, profiles or rates. |
| **Office**            | Calendar, families, attendance, collections, leads and hours. No Finance, costs or pay.                 |

![Team › Access: what each role can do](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-44f3d8094679024ae66d3fc3a748522667ca7372%2Fteam-access.png?alt=media)

{% hint style="info" %}
What a role can't see is never sent to its browser. It isn't hidden: it isn't sent at all.
{% endhint %}

## Two extra permissions: Finance and Reports

On top of the role, each person's profile (**Team › person › Access**) has two switches:

* **Finance**: opens the **Finance** section. It only works with the Direction or Financial Control roles.
* **Reports**: opens the **Reports** section, whatever the role.

![A person's Access tab](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-936b8c6f00760d6704582326c982e76786c5524d%2Fperson-access.png?alt=media)

If someone is missing one of these sections from their menu, they're most likely missing one of these switches.

## Who decides what (summary)

| Action                                               | Who                             |
| ---------------------------------------------------- | ------------------------------- |
| Invite someone to the CRM or change their role       | Direction                       |
| Change rates and prices outside the price list       | Direction                       |
| Create or change class passes                        | Direction                       |
| Set a team member's pay conditions                   | Direction                       |
| Decide and close extra hours                         | Direction                       |
| Upload payslips                                      | Direction and Financial Control |
| See and export VAT                                   | Direction and Financial Control |
| Close a VAT quarter                                  | Direction                       |
| See leads, take payments, take attendance, log hours | Every role                      |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.echevarrisports.com/guia/en/getting-started/roles-y-permisos.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.