> For the complete documentation index, see [llms.txt](https://docs.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umh.app/management-console/authentication/sessions.md).

# Sessions

Regardless of which [authentication method](/management-console/authentication.md) your account uses, session timeouts apply the same way.

## Session Durations & Renewal

Your session is managed by the Management Console itself, independently of the identity provider.

| Session rule   | Value                                                                                        |
| -------------- | -------------------------------------------------------------------------------------------- |
| Session length | 14 days                                                                                      |
| Renewal        | While you are active and within 7 days of expiry, the session is extended by another 14 days |
| Hard limit     | 30 days after you first signed in, you sign in again regardless of activity                  |
| Ends on        | Sign-out, the 30 day limit, or removal from the company                                      |

## One session per account

Each account has one active session at a time. When you sign in from another device, the existing session is invalidated and you are signed out of the Management Console everywhere else.

This is intentional. Most work in the Management Console is a one-off change, often to a single umh-core instance. Allowing several sessions at once would let the same account push concurrent, conflicting changes to your umh-core instances.

{% hint style="warning" %}
There is no automatic sign-out after a period of inactivity. A session stays valid until the 14 day token expires or the 30 day limit is reached, whichever comes first. Sign out when you leave your workstation.
{% endhint %}


---

# 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.umh.app/management-console/authentication/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.