GOVERNANCEOS / SESSION & ACCESS
Session & access
Review your current application session. Feature licensing, operator permissions and operational write gates apply independently.
Current session
Sessions end at token expiry or after eight hours, whichever is earlier. Access is withheld during the final minute. Sign-out revokes the current application session, including its use on other nodes; it does not sign out all Microsoft sessions or other devices.
How session checks work
Protected operations recheck the server session on every request. A storage failure denies access. Licence and role checks remain separate. The application rechecks active sessions on return to the tab and periodically while visible; already downloaded files cannot be withdrawn.
Local single-instance storage is suitable for the existing local setup. Shared Redis storage must be explicitly configured by your administrator. The storage label does not establish production readiness, failover safety or completed service acceptance.