> 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/pam/concepts/session-management.md).

# Session management

Session management in Devolutions PAM injects credentials directly into remote sessions in real time, keeping passwords hidden from end users.

**Session management** enables secure, real-time injection of credentials directly into an active access session, without ever revealing the actual credentials to the user. This includes support for sessions that require multifactor authentication (MFA), such as Web Jump Access.

By keeping credentials hidden and only brokering them at the moment of connection, session management helps protect [privileged accounts](/pam/concepts/privileged-account.md) from exposure, misuse, or theft. This approach is central to the security strategy of solutions like Devolutions PAM and Remote Desktop Manager, which ensure only authorized access occurs without user visibility into credential values.

Use cases include scenarios where users initiate remote desktop, SSH, or web sessions but are not permitted to see or reuse passwords. These workflows can be interactive, automated, or triggered by events, and can leverage integrations with external PAM systems or password managers.

#### Session management aliases

* credential injection
* credential brokering
* just-in-time access

#### Related topics

* [External PAM integrations](https://docs.devolutions.net/rdm/concepts/advanced-concepts/external-pam-integrations)
* [Password management](https://docs.devolutions.net/rdm/concepts/basic-concepts/password-management)
* [Security](https://docs.devolutions.net/rdm/concepts/advanced-concepts/security)
* [Session management](/pam/concepts/session-management.md)


---

# 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/pam/concepts/session-management.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.