> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/admin/configuring-a-self-hosted-instance/timeouts.md).

# Setting timeouts for session inactivity and length

By default, Structural does not have an automatic timeout based on inactivity or session length.

## Setting a timeout based on user inactivity <a href="#timeout-inactivity" id="timeout-inactivity"></a>

To have a session time out based on user inactivity, set the following [environment setting](/app/admin/environment-variables-setting.md):

`TONIC_INACTIVITY_TIMEOUT_IN_SECONDS`

For example, if you set this to `60`, then after a session is inactive for 60 seconds, the session ends.

You can configure this setting from the **Environment Settings** tab on **Structural Settings**.

## Setting an overall maximum length for a user session <a href="#timeout-session-length" id="timeout-session-length"></a>

To automatically end a user session when it reaches a maximum length, set the following [environment setting](/app/admin/environment-variables-setting.md):

`TONIC_MAXIMUM_SESSION_LENGTH_IN_HOURS`

For example, if you set this to `3`, then when the session length reaches 3 hours, the session automatically ends and the user must reauthenticate.

You can configure this setting from the **Environment Settings** tab on **Structural Settings**.


---

# 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.tonic.ai/app/admin/configuring-a-self-hosted-instance/timeouts.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.