> For the complete documentation index, see [llms.txt](https://doc.simax.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.simax.fr/fonctionnelle/ressources-humaines/tableau-de-bord-rh.md).

# Tableau de bord RH

Un tableau de bord RH est un outil de pilotage qui centralise des indicateurs clés des ressources humaines afin de suivre les effectifs, la performance sociale et d’aider à la prise de décision.

Dans SIMAX, le tableau de bord RH permet de visualiser les congés en attente de validation, les absences, ainsi que les fins de contrat et de période d’essai.

### Contexte :&#x20;

***Voici le cas d'une entreprise NeoTerra spécialisée dans technologie durable :***&#x20;

Camille, responsable des Ressources Humaines de l’entreprise, commence sa journée en consultant le tableau de bord RH dans SIMAX afin d’avoir une vision globale des congés, absences et échéances contractuelles à traiter.

Implémentation :&#x20;

Vous pouvez aller dans **RH > Tableau de bord RH.**&#x20;

<figure><img src="https://1324884545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBJ3Kpe0vg6NlDz0QDIX%2Fuploads%2FalkZx5KWzrUxABztWaWE%2FTableau%20de%20bord%20RH.PNG?alt=media&amp;token=1e792292-9eaf-446d-ab86-1c42cef65930" alt=""><figcaption></figcaption></figure>


---

# 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://doc.simax.fr/fonctionnelle/ressources-humaines/tableau-de-bord-rh.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.
