# Session Settings

### Overview

Network administrators can implement session management policies to control user access by restricting the number of concurrent sessions allowed per user and by setting session timeouts for web and mobile platforms. These policies provide stronger security, reduce risks from unattended sessions, and give administrators and users flexibility to manage their own experience.

<img src="/files/KepVYnDRNCcaosYBCSLa" alt="" width="563">

Administrators can configure session management through the **Admin Portal**, while end users can customize their own preferences in **Change My Settings**. Additionally, administrators have the capability to force sign out all active sessions across all platforms as a security measure. This action instantly logs out all users except the administrator, ensuring heightened security but potentially causing users to lose unsaved data.

***

### Session Timeout Settings

MangoApps provides separate session timeout settings for **Web** and **Mobile** platforms, ensuring more flexibility and a better user experience.

**Admin Settings**:

* Configurable in **Admin Portal > Security > Session Settings**.
* Timeout values available: Never, 10 mins, 30 mins, 90 mins, 1 hour, 4 hours, 8 hours, 12 hours, 24 hours, 48 hours.
* Defaults:
  * **Web Sessions**: “Never” for new domains; existing domains retain their current configuration.
  * **Mobile Sessions**: “Never” for new domains; for existing domains, mobile inherits prior setting (either “Never” or matches web session timeout).

**User Settings**:

* End users can override admin defaults in **Change My Settings > Timeout**.
* Both **Web Session Timeout** and **Mobile Session Timeout** are available with the same set of values.
* Users can choose “Never” to keep sessions active indefinitely.

**Impact of Settings**:

* Web session timeouts apply only to web sessions and do not affect mobile sessions, messenger, or recorder sessions.
* Mobile session timeouts apply only to mobile sessions and do not affect web sessions, messenger, or recorder sessions.

***

### Concurrent User Sessions

**Concurrent Sessions**: MangoApps allows users to have concurrent sessions per platform (Web, Mobile, Desktop).

**Maximum Sessions**: Administrators can set the total number of concurrent sessions per user per platform, with a maximum of **five sessions per platform**.

**Save**: Click the **Save** button to apply the selected concurrent session settings.

***

### Force Signout Options

**View Active Sessions**: The system displays all active sessions of the domain.

**Force Signout**: Admins can immediately end all user sessions across all platforms.

**Expire All Sessions Except Mine**: Admins can log out all users across all MangoApps platforms while keeping their own session active.

{% hint style="danger" %}
Forcing signout immediately ends user sessions, which may result in loss of any unsaved data.
{% endhint %}

{% hint style="info" %}
If a users logs in on more than the specified session on any platform the oldest session automatically expires and the same is recorded in the [User Access Log](https://guides.mangoapps.com/admin-guide/home/logs/user-access-log).
{% endhint %}


---

# 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://guides.mangoapps.com/admin-guide/security/session-settings.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.