TROUBLESHOOTING
Check identity, school context, role, route, and service state in that order.
Use the smallest safe diagnostic path, preserve useful error context, and contact support when the issue depends on private account or institution data.
Before you begin
- The intended account email and route
- Approximate issue time
- No passwords or tokens
Signed in but still see Sign in
Refresh once and confirm the authenticated account in the header. If the identity session is valid but the header remains stale, sign out through the provided control and sign in again rather than clearing random browser data.
Existing school but setup is requested
Open the account dashboard and allow the accessible-school check to finish. Confirm the intended account email. Do not register the same institution again. If the existing active school is not found, contact support with the route, time, and non-sensitive account identifier.
Access denied or missing module
Confirm the current school or tenant context, assigned role, enabled module, record state, and task ownership. Ask the responsible administrator to review access rather than sharing another user account.
Useful support evidence
Provide the affected page, expected result, actual result, approximate time, browser type, and visible error reference. Remove student data, credentials, tokens, and unrelated screenshots.
Scope and limitations
- Public troubleshooting cannot inspect or disclose a private account or tenant record.