> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/fr/plateforme/user-sessions.md).

# Sessions utilisateur

Consultez les détails des sessions utilisateur dans PowerShell Universal, y compris l'horodatage, l'utilisateur, la source, la chaîne de l'agent utilisateur et l'adresse IP distante pour chaque connex

Lorsque les utilisateurs accèdent à PowerShell Universal via la console d'administration ou l'appli, les sessions sont stockées dans la base de données. Les informations sur les sessions comprennent :

* Horodatage
* Utilisateur
* Source
* Chaîne de l'agent utilisateur
* Adresse IP distante

Pour accéder aux sessions utilisateur, cliquez sur Accueil, puis sur la carte Sessions utilisateur.


---

# 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.devolutions.net/powershell-universal/fr/plateforme/user-sessions.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.