Session Management

Session management is the operational lever that makes the rest of the security model actionable. Without it, an Org Admin who suspects a compromised account or a peer mentor who has left the organization has no way to force a sign-out - they can only deactivate the account and wait for tokens to expire. Visible session control closes that gap and is a standard expectation for any platform handling sensitive personal data. It also supports the workforce realities of the peer-mentor model: volunteers leave, devices are lost, certifications expire, and coordinators sometimes need to revoke access immediately rather than at the next natural session boundary. Pairing session control with audit logging gives organizations the tooling they need to demonstrate to Bufdir and to their members that access to data is actively governed.

Implementation uses the user_sessions store populated by the Authentication Module and exposes a Session Service in the admin portal that queries and revokes sessions through the auth module's stable API contract - no direct reads of auth-internal tables. The Session Management Page provides filtering by user, role, product, and last-active time, with bulk-revoke for incident response. Revocation must work uniformly for mobile (token rotation invalidated, app falls back to login on next refresh) and admin portal (HTTP-only cookie session invalidated server-side). Every revoke action writes an audit entry through the Audit Service. Tenant scoping ensures Org Admins see only their own organization's sessions; Global Admins see cross-org sessions only via the explicit support-access flag.