Manage account sessions
The Sessions screen can show the active session records associated with your account. Use it to distinguish the session marked Current from other listed sessions and to choose an individual or bulk revocation request.
Availability
Open Profile, then select Sessions. What appears depends on the account's session strategy:
- When tracked sessions are enabled, the screen loads a list with creation and validity dates. The session associated with the current token can be marked Current.
- When tracked sessions are not enabled, the screen shows an Active sessions action instead of the list. That action submits a request to change the session setup; it does not prove that the strategy changed.
The list contains valid, unexpired records returned for the signed-in account. Its order is not a reliable indicator of which session was used most recently.
State and result matrix
| State or control | What the Driver App shows | Request boundary | What to verify |
|---|---|---|---|
| Loading | Placeholder rows | No session change | Wait for the list to finish loading |
| Populated list | Creation and validity dates for each row | No session change | Identify the row marked Current, if present |
| Current row | The record matched to this app's token | Closing this row requests revocation of the current record | Expect the app to begin local sign-out only after a response without an error |
| Other row | A listed record without the Current label | Closing this row requests revocation of that record | Reopen the list and confirm the row is no longer returned |
| Close icon | Are you sure to delete this session? | Selecting the confirmation action sends one revocation request | The dialog closing is not proof of deletion |
| Delete all sessions | Confirmation includes the current record | Sends a bulk request that includes the current record | Verify local sign-out and later account access separately |
| Delete all sessions except current | Confirmation preserves the current record | Sends a bulk request that excludes the current token's record | Reopen the list and verify only the current record remains |
| Active sessions | Confirmation asks to enable session tracking | Sends a strategy/bulk-session request | Sign in again or reopen Sessions and verify that a tracked list is available |
| Empty message | You don't have any sessions | No session change | If unexpected, leave and reopen the screen; an empty view alone is not proof that no records exist |
| Action in progress | Bulk buttons are disabled | A prior request is still unsettled | Wait; do not submit the same action again |
Confirmations and session choices
Every close or bulk action opens a confirmation first. Review the wording before you continue:
- Closing an individual Current row can end this app's local session after the revocation response.
- Closing another row leaves the current row selected in the app.
- Delete all sessions includes the current record.
- Delete all sessions except current preserves the record matched to the current token.
The confirmation closes as soon as the callback starts. Wait for the screen to settle, then reopen Sessions to verify the returned records. Do not assume that another device signed out just because a row disappeared locally.
Platform, permission, and lifecycle behavior
Session management uses the signed-in account and does not request location, camera, contacts, or notification permission from this screen. The list and confirmation layout can vary with screen size and platform, but the same current-versus-other choices apply.
If the current session is included, the Driver App can remove local token and user data after the session response. That local cleanup is asynchronous and is not the same workflow as the dedicated Sign out action.
Effects and boundaries
Session actions can change server session records, an audit log, the list held by the app, and local authentication storage. These effects do not settle as one proven transaction:
- A session record can change before audit logging finishes.
- The app can update its visible list before another installation observes the change.
- Local cleanup after removing the current session can finish separately from the server response.
- This screen does not prove cleanup of notification tokens, availability, sockets, queued work, or provider state.
Because the running backend version is not established by this documentation, the guide does not claim deletion success or immediate remote-device sign-out.
Troubleshooting
- If a removed row returns, refresh the screen once and confirm you selected the intended record.
- If the screen unexpectedly says You don't have any sessions, leave and reopen it before concluding that the list is empty.
- If Active sessions remains after confirmation, do not repeat it rapidly. Sign in again or ask an administrator to verify the account's session setup.
- If you removed the Current row but remain in the app, avoid sensitive actions. Close and reopen the Driver App, then verify whether sign-in is required.
- If another device still appears signed in, do not rely on the local row alone. Ask an administrator to verify the account's current session records.
Related guides: Driver App overview · Understand startup and loading · Sign in as a driver