Use and recover a console sign-in
Purpose
People use sign-in to begin console work and recovery when credentials no longer work. Session handling keeps them informed when renewal fails so they can distinguish sign-in problems from temporary provider trouble.
How It Works
The user starts at password sign-in or the supported Google path. After success, safe navigation returns them to the console work they requested. A reload restores a session through the refresh cookie rather than a persisted access token. The browser renews access when needed and explains a terminal refusal. Temporary provider trouble can leave the existing valid session usable. Sign-out removes that session’s access to protected navigation. Someone who forgot a password follows the code sent by recovery and then signs in using the replacement password. Administrators can initiate recovery for members they are authorized to manage. Membership checks and cached authorization have different freshness limits, so account removal must not be described as immediate on every possible request.
Relationships
- Invitation acceptance supplies the established console identity.
- Security context presents the workspace and permissions after sign-in.
- User administration owns suspension, reinstatement and removal; authorization owns cached grant evaluation.