Session Maintenance
The Session Maintenance page shows every signed-in session across the system, so you can find and sign out a specific device without having to look up the user first.
Who Uses This
- Application Administrator
- System Administrator
Navigation Path
- Administration menu → Session Maintenance
The Sessions Grid
- Each row shows the user (name and email), device, browser, operating system, app platform and version, IP address, when the session signed in, when it was last active, whether it stays signed in, and when it expires. Your own current session is marked This Device instead of a connection status.
- The Status column shows whether a session currently has an active connection to the server. This is a snapshot taken each time the grid loads rather than a continuously live indicator, and mobile app sessions never show as connected even while signed in, since they don't hold an open connection the way a browser session does.
- Filter, sort, and page the grid like any other SmartSub grid. Signed In, Last Active, and Expires can be sorted but not filtered, since they're compared in a different time zone than what's displayed.
- Click the sign-out icon on a session's row to revoke that one session. Confirm the action to sign that device out immediately.
Managing an Individual User's Sessions
- On the User Maintenance page, click the Manage Sessions icon on a user's row to open a popup listing that user's sessions, with the same device detail as the Session Maintenance grid.
- Use the sign-out icon on an individual session, or click Sign Out All Sessions to revoke every session for that user at once (with confirmation). This icon is only available to Application and System Administrators, even though Reseller Administrators can also access the User Maintenance page.
Password Resets End Sessions Immediately
- Resetting a user's credentials from the User Maintenance page immediately signs that user out of every session. This isn't called out separately — the only confirmation shown is that the password reset succeeded.