> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/settings/session-management.md).

# Session Management

See who is signed in to Tellius, on which device and from where, end login sessions, and manage the sessions behind embedded Tellius links.

**Settings → System → Session Management** has two pages:

* [**Manage Sessions**](#manage-sessions): the login sessions of people signed in to Tellius, with the device and IP address of each, and a way to end a session.
* [**Active Login Sessions**](#active-login-sessions): the sessions behind embedded Tellius links, such as an embedded Kaiya, grouped by the embedded resource.

### Manage Sessions

Under **Settings → System → Session Management → Manage Sessions**, you see the active login sessions and can end them. Administrators see their own sessions. Super users see every user's sessions and can filter them by user.

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FPpslKfklji4mzi3bGPQl%2Fmanage-sessions-64.png?alt=media&amp;token=7d6bb6e2-1ba7-4f3e-add3-d534ae9eba49" alt="The Manage Sessions page with the User filter and the search box highlighted, and a list of sessions with user, login time, last active, expiry, device, IP address and End session" width="563"><figcaption></figcaption></figure>

Each row is one session, and the session you're using now is marked **Current**. The columns are:

* **User:** the account that is signed in.
* **Login time:** when the session started.
* **Last active:** the last time the session was used.
* **Expires in:** how long until the session ends on its own.
* **Device / browser:** the browser and operating system the session came from.
* **IP address:** the address the session came from.
* **Action:** **End session** signs the user out on that device.

To find sessions:

* **User** (super users): choose **All users** or one user. Type in the search box at the top of the list to find a user.
* **Search by session ID, user, device, or IP…:** type part of a session ID, user name, device or IP address, then select **Search**.
* **Refresh sessions** (the circular arrows): reloads the list.

When the list is long, use the page controls under it.

To end a session, select **End session** in its row and confirm. The user is signed out on that device. A message confirms that the session has ended.

{% hint style="success" %}
**When to end a session.** End a session when someone reports a lost or shared laptop, when a session comes from a device or IP address you don't recognize, or right after you remove someone's access, so they're signed out at once instead of when the session expires. Check **Device / browser** and **IP address** before you end it, so you don't sign out the wrong device.
{% endhint %}

### Active Login Sessions

Under **Settings → System → Session Management → Active Login Sessions**, super users see the sessions opened through embedded Tellius links, such as a Kaiya, Vizpad or Search embedded in another application. Each row is one embedded resource.

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FU0WKZVg1uBzKl0og3MfL%2Factive-login-sessions-64.png?alt=media&amp;token=940c0da7-01de-48a1-8fd3-4de5e868a427" alt="The Active Login Sessions page with the Session Type filter, search box and a list of embedded resources, with a row&#x27;s menu open showing Copy Link, Open Link and End Session" width="563"><figcaption></figcaption></figure>

The columns are:

* **Resource:** what is embedded, such as **Kaiya**.
* **Sessions:** how many sessions are open on it.
* **Expires In:** how long until the sessions end. The tag turns from green to amber and then red as the sessions near their end, and gray once they have expired. Hover over it to see the time left.
* **Actions:** the three-dot menu.

To narrow the list:

* **Session Type:** shows one kind of embedded session: **All**, **Assistant**, **Dashboard**, **Discover**, **Extension**, **Kaiya**, **Feed** or **Search**. Other kinds appear in the list when sessions of that kind exist.
* **Reset:** clears the filter.
* **Search:** finds a session by the text you type.
* **Refresh** (the circular arrows): reloads the list.

The three-dot menu in a row has three options:

* **Copy Link:** copies the embed link to the clipboard.
* **Open Link:** opens the embedded resource from its link.
* **End Session:** ends every session that uses this embed link. Tellius asks you to confirm first.

{% hint style="warning" %}
**Ending an embed session can't be undone.** Everyone using that embed link loses access at once, and the link stops working. Create a new embed link afterwards if people still need it. See [What you should know before embedding](/tellius-6.4/embedding-tellius/what-you-should-know-before-embedding.md).
{% endhint %}

### Who can see these pages

* **Manage Sessions:** administrators and super users. Administrators see only their own sessions. A custom role reaches it with **Manage workspace** under **Administration**.
* **Active Login Sessions:** only super users.

See [Custom roles](/tellius-6.4/settings/users-and-access/custom-roles.md).


---

# 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://help.tellius.com/tellius-6.4/settings/session-management.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.
