Short answer
Start security review by confirming the account, session, workspace, route, and permission state.
When to use this
Use this article when access looks wrong, a private surface appears public, or a role seems too broad.
Requirements
Use a trusted device and avoid sharing private access details in public channels.
Checklist
Confirm the signed-in account, workspace, role, route, browser session, and last action. Capture safe evidence before changing anything.
Common problems
Many apparent security issues are caused by using the wrong account, stale browser sessions, or a workspace role that differs from a personal role.
Related articles
Read Roles and permissions for access context.
Escalation guidance
For security concerns, include safe screenshots, route, account role, workspace role, and the exact access behavior.
Related articles
Roles and permissions
Learn how account roles, workspace context, and admin surfaces affect what you can see or change.
Share support context safely
Know what to include and what to hide when asking for help with account, billing, AI, or workspace issues.
Was this article helpful?
Your feedback helps Probe improve articles, search synonyms, and support triage.