> 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/acceso.md).

# Signing in to the CRM

## Sign in

1. Open `https://<club-domain>/admin`.
2. Enter your email and password and click **Sign in**.
3. If you don't remember your password, click **Forgot your password?** and you'll get an email with a link to set a new one.

![The sign-in screen](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-a82d9a2e4fc04b983b21e4d930536930e0228bde%2Flogin.png?alt=media)

{% hint style="warning" %}
If you see **No access** after signing in, your account exists but isn't registered as club staff. Ask Direction to invite you from **Team › Access › Invite user**.
{% endhint %}

## The sidebar

On the left (or along the top on a phone) is the menu with every section. You only see the ones your role can open (see [Roles and permissions](/guia/en/getting-started/roles-y-permisos.md)).

![The sidebar](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-b6b97723013c3f712586fde32759d6322f854f91%2Fsidebar.png?alt=media)

| Section       | What it's for                                              |
| ------------- | ---------------------------------------------------------- |
| **Dashboard** | The summary of the day, week or month                      |
| **Calendar**  | Classes and sessions, coaches and courts                   |
| **Leads**     | Everything that comes in from the website forms            |
| **Academy**   | The season's students, groups, attendance and class passes |
| **Camps**     | Camps, their weeks or days and the children booked         |
| **Payments**  | Who owes, payment links and what has been received         |
| **Finance**   | P\&L, costs, bank, invoices, VAT and the accountant export |
| **Reports**   | How clients, marketing and the Academy are evolving        |
| **Team**      | People, hours, payslips and access                         |
| **Emails**    | A preview of every email the system sends                  |
| **Shop**      | Coming soon                                                |
| **Bin**       | Bring back what was deleted                                |
| **Audit**     | Who did what and when                                      |

At the bottom you'll find:

* **Undo**: reverts your last change (it asks first). When there's nothing to revert it says **Nothing to undo**. **Recent changes** opens the full list.
* **Your photo and name**: open your profile in Team.
* **The flag** (language), **the sun or moon** (light or dark mode) and **sign out**.

![Undo and Recent changes](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-bfa6bd1f30901acfb87d3dcb3954de8ca0c56996%2Fundo.png?alt=media)

## Other ways in

The CRM is for club staff only. Coaches and families have their own apps:

* **Coaches**: `/coach`. They see their sessions, take attendance and check their hours, with no prices or money. Access is given from the coach's profile in **Team › person › Access**. The same login opens both the coach app and the CRM.
* **Families**: `/family`. They see their bookings, children and payments, and sign in without a password using a link they get by email.


---

# 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/acceso.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.