Manage account sessions
Use Sessions to review the valid, unexpired session records returned for your account. You can request that one session be closed, close all sessions, or preserve the session marked Current while closing the others.
Before you start
- From the authenticated workspace, open Profile, then select Sessions.
- Identify Current from the label in the list. The dates are creation and validity dates; they do not identify a device or prove recent activity.
- Treat every close action as destructive. If you cannot identify a row safely, leave it open. In particular, do not close Current unless you are prepared to lose access and have an approved access-restoration path.
Complete the task
- Wait for the session list to finish loading.
- Review the creation and validity dates and locate the row marked Current, if one is present. Do not infer a device, browser, location, or owner from the row order or dates.
- Choose the narrowest action:
- Select the close icon on one row to request that only that session be closed.
- Select Delete all sessions except current to preserve the record matched to this app's token.
- Select Delete all sessions only when you intend to include Current and are ready to lose access in this app.
- Read the confirmation carefully. Confirm only when its scope matches the intended effect, then wait for the action to settle. Make exactly one attempt for the selected session or bulk action.
If the account does not yet use tracked sessions, the screen shows Active sessions instead of a list. Its confirmation requests a session-strategy change while preserving the current token record; it is not proof that the change completed.
Verify the result
After exactly one destructive attempt, leave and reopen Sessions exactly once. This is the only verification read:
- For another listed session, check whether that exact row is still returned. A row disappearing does not prove that a specific device stopped immediately.
- For Delete all sessions except current, check whether the row marked Current remains. Do not rely on list order.
- If the action included Current, the authenticated workspace may no longer be available on this single read.
- Treat any returned row, missing Current row, unexpected empty list, partial-looking result, or unclear state as unknown. Stop and ask an administrator or Ordering Support to verify the session records and provide access-restoration evidence. Do not reopen the screen or app again and do not take another authentication or session action.
Recover safely
| What you observe | What it means | Safe next action |
|---|---|---|
| A removed row returns on the single verification read | The result is unknown: the request may be missing, partial, stale, or affected by a later failure after deletion | Stop; do not reopen or act again. Ask an administrator or Ordering Support to verify the records and provide access-restoration evidence |
| Current is missing while the authenticated workspace remains available | Server and local sign-out effects may have settled separately | Avoid sensitive work and stop; do not reopen or act again. Use administrator or Ordering Support verification |
| Another installation still appears signed in | This screen cannot prove immediate remote-device enforcement | Do not guess which row belongs to that device and do not act again; ask an administrator to verify the records |
| You don't have any sessions appears unexpectedly on the single verification read | The returned state is empty, unavailable, stale, or otherwise unknown | Stop; do not reopen or act again. Escalate for record and access-restoration evidence |
| Active sessions remains on the single verification read | The strategy result is unknown; the earlier closed dialog did not verify it | Stop; do not reopen or act again. Ask an administrator or Ordering Support for session-setup and access-restoration evidence |
Availability and platform differences
The tracked list is shown when the signed-in account reports the tracked-session strategy. It contains only valid, unexpired records returned by the service. Each record can contain internal device information, but the Business App screen does not display a device name, browser, operating system, or location. The layout can vary by screen size or platform without changing these boundaries.
Closing Current or choosing Delete all sessions can clear this app's stored token and user state after a response without an error. Socket shutdown and another installation's cached or already-open state can settle separately, so this guide does not promise immediate remote sign-out.
Related articles
:::note Visual status authorized synthetic capture program with accepted exact asset allowlist and independent visual QA :::