> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/sessions/session-management.md).
# Session Management
## Session Management
Use this page to find, search, filter, and organize your test sessions.
### Accessing the Sessions list
You can open the Sessions list from two places, depending on the session type:
* **Interactive → Sessions** shows sessions from manual interactive testing across Web, Mobile, and TV.
* **Automation → Sessions** shows sessions from automation frameworks such as Playwright and Appium.
Both pages use the same layout.
A tab bar at the top lets you switch between platforms or frameworks without leaving the page.
### Understanding the session table
Each row in the table represents one test session.
The default columns are:
| Column | Description |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Build Name** | Display name of the session. You can rename it inline. |
| **Start Time** | Time the session started, shown in your local timezone. |
| **Duration** | Total session length. |
| **Status** | Session outcome, such as `Passed`, `Failed`, or `Stopped`. |
| **Config** | Primary and secondary configuration. For web sessions, this is OS and browser. For mobile and TV sessions, this is the device name. |
| **Tags** | Labels attached to the session. You can add or remove them inline. |
| **User** | Email address of the person who ran the session. |
| **Actions** | Quick access to Video, Screenshots, Bugs, and Notes without leaving the list. |
### Inline editing
You can rename a session and manage its tags directly from the list.
To rename a session, click the name cell to enter edit mode.
Press `Enter` or click outside the field to save.
To manage tags, click the tags cell to open the tag picker.
From there, assign existing tags or type to create a new one.
### Searching sessions
The search bar at the top-right of the Sessions list supports two modes.
Use the toggle next to the input field to switch between them.
#### Plain text search
Type any word or phrase.
The portal matches it against the session name, session ID, start time, status, configuration, user email, and tags.
Use this mode when you remember any identifying detail.
#### JQL search
Use JQL mode for precise filtering.
Queries follow the format `field = "value"`.
Combine multiple conditions with `AND`.
Examples:
| Query | Result |
| -------------------------------------------------- | --------------------------------- |
| `status = "failed"` | All sessions with status `Failed` |
| `user = "alice@example.com"` | Sessions run by a specific user |
| `status = "failed" AND user = "alice@example.com"` | Failed sessions run by that user |
### Filtering sessions
Click **Filter** to open the filter panel.
Filters are grouped by:
* Status
* User
* OS
* Browser
* Device
* Resolution
* Build Name
* Tags
You can select multiple values within one group.
Within the same group, filtering works as `OR`.
Across different groups, filtering works as `AND`.
Active tag filters appear as blue chips below the toolbar.
Click **Filter** again to adjust or clear them.
### Controlling column visibility
Click **Columns** next to **Filter** to choose which columns appear in the table.
The Session ID column is hidden by default to reduce clutter.
Enable it when you need to copy session IDs.
### Pagination
The table loads 20 sessions per page by default.
Use the controls at the bottom of the table to move between pages.
You can also change the page size to `10`, `20`, `50`, or `100`.
{% hint style="info" %}
Search and filter apply only to the data loaded on the current page.
If you need older sessions, paginate first, then search.
You can also reduce the page size to keep recent sessions on the first page.
{% endhint %}
### Quick-access modals
The **Actions** column includes four icon buttons that open lightweight modals without leaving the Sessions list.
Use them to quickly review session evidence:
* **Video** opens an in-place video player for the full recording.
* **Screenshots** opens a gallery of captured screenshots.
* **Bugs** lists bugs filed during the session.
* **Notes** displays session notes.
For deeper analysis, click anywhere on a session row outside the **Actions** column.
The portal opens the full [Session Details](/appx_documentation/test-infrastructure-documentation/sessions/session-details.md) page in a new browser tab.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/sessions/session-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.