## Configure session timeouts

URL: https://docs.atlan.com/product/capabilities/governance/users-and-groups/how-tos/manage-user-authentication

> Set how long an Atlan session stays valid before it expires. Configure idle timeout, max timeout, and Remember Me settings for all users in the workspace.

Session timeouts control how long a user stays signed in to Atlan before they must authenticate again. Configuring them lets you align Atlan with your organization's session security policy. The settings apply to every user in the workspace regardless of whether they signed in via basic authentication or SSO. When a session expires, all tokens and browser sessions become invalid.

## Prerequisites

- You are an **admin** in Atlan.
- Atlan uses defaults for any field you leave blank: you only need to set the values you want to change.

## Configure session timeouts

1. In your Atlan workspace, click **Settings** from the left menu.

 If you are using the **Old UI (Classic)**, from the left menu, click **Admin**.

2. Click **Authentication** to open the authentication settings.

3. Next to _Session settings_, click the **Edit** button. The _Change session settings_ dialog opens.

4. For each timeout you want to configure, enter a numeric value and pick a unit (**Minutes**, **Hours**, or **Days**) from the dropdown. All values accept between 1 minute and 30 days.

 - **Session idle timeout:** how long a session can sit idle before it expires. Minimum 1 minute.
 - **Session max timeout:** the total maximum lifetime of a session, regardless of activity. Must be equal to or greater than the idle timeout.
 - **Remember me session idle timeout:** idle timeout for sessions where the user checked "Remember me" at sign-in. Leave blank to use the default (7 days).
 - **Remember me session max timeout:** maximum lifetime for Remember-me sessions. Must be equal to or greater than the Remember-me idle timeout. Leave blank to use the default (4,745 days).

5. Click **Save changes**. The new values apply to all subsequent sign-ins immediately. Existing sessions are not invalidated and continue under whatever settings were in effect when they were created.

## Need help?

If users are being signed out sooner than expected, check whether their IdP is enforcing a shorter timeout. SSO sessions cannot outlive the IdP-side session. Contact [**Atlan Support**](https://docs.atlan.com/support/submit-request) if Atlan's session settings aren't behaving as configured.

## See also

- [Set up authentication](https://docs.atlan.com/llms/governance/access-control/authentication-and-authorization/llms.txt): Configure SSO before tuning session timeouts in a production workspace.
- [Restrict auto user creation](https://docs.atlan.com/llms/governance/access-control/limit-sso-automatically-creating-users-when-they-log-in/llms.txt): Lock down who can be auto-provisioned via SSO.

---