# Session Management

Verkada's enhanced session management feature ensures an efficient and secure user experience.

***

## Maximum session duration

The **Maximum Session Duration** control manages the time period after which a user is logged out, regardless of activity history.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}

{% step %}
**In the left navigation, select Login & Access > Session Management.**
{% endstep %}

{% step %}
**Locate and set the Maximum Session Duration:**

* Default: 60 days
* Min: 1 day
* Max: 180 days
  {% endstep %}
  {% endstepper %}

***

## Idle timeout

This control specifies the maximum period of inactivity after which a user is logged out. If a user has not used Command in over the specified time, they are logged out regardless of whether maximum session duration has been reached.

{% hint style="warning" %}
The **Idle Session Timeout** value can never be greater than the **Maximum Session Duration** value.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}

{% step %}
**In the left navigation, select Login & Access > Session Management.**
{% endstep %}

{% step %}
**Locate and set the Idle Timeout:**

* Default: 7 days
* Min: 15 minutes
* Max: 30 days
* Government Command organizations default to 1 hour
  {% endstep %}
  {% endstepper %}

***

## Customize login lockouts

Control the number of unsuccessful login attempts and lockout behavior.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}

{% step %}
**In the left navigation, select Login & Access > Session Management.**
{% endstep %}

{% step %}
**Set the Allowed Login Attempts** (unsuccessful attempts within 15 minutes before lockout):

* Default: 6 attempts
* Government Command organizations default to 3 attempts
  {% endstep %}

{% step %}
**Set the Lockout Period** (time until automatic unlock):

* Default: 15 minutes
* Government Command organizations default to 30 minutes
  {% endstep %}
  {% endstepper %}

***

## Limit concurrent user sessions

This control specifies the maximum number of active sessions a user can have at any given time.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}

{% step %}
**In the left navigation, select Login & Access > Session Management.**
{% endstep %}

{% step %}
**Set the Maximum Sessions per User:**

* Default: Unlimited sessions
* Government Command organizations default to 2 sessions per user
  {% endstep %}
  {% endstepper %}

{% hint style="warning" %}
**Session** refers to a web/mobile instance of Command and extends to the Verkada Pass app (but not other native product-specific apps).

* Being logged in on 10 different tabs in the same browser = 1 unique session
* Being logged in on 2 different browsers = 2 separate sessions
* Being logged in on desktop, mobile browser, and mobile app = 3 separate sessions
  {% endhint %}

For the Pass app, if the active session maximum is reached, previously logged in users will be logged out and have their BLE credentials revoked until a new active login is established.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.verkada.com/command/security/authentication-overview/session-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.