Access issues

Use this guide when users cannot sign in to Opsflw Connect or cannot access expected application resources after sign-in.

Common symptoms

• Sign-in fails or loops back to login
• User can sign in but sees no applications
• User can open Opsflw Connect but gets permission errors
• Access worked before and stopped after role or organization changes

Typical causes

• Missing or outdated role assignment
• Identity provider group membership not yet propagated
• Access scope mismatch for tenant, subscription, or environment
• Conditional access or network policy preventing successful sign-in

What end users should do

1. Confirm you are using the expected organization account.
2. Sign out and sign in again to refresh session and token claims.
3. Verify with your administrator that your role assignment is active.
4. Confirm your access request covers the correct environment and instance.
5. If access still fails, submit a support ticket with error details.

What to include in your support ticket

• User email and organization/tenant name
• Application and environment you tried to access
• Time of failure (UTC)
• Screenshot or exact text of the error message
• Confirmation of recent role or team membership changes

Expected outcome

Opsflw support will validate access scope, role mapping, and policy alignment, then provide the required remediation steps and estimated restoration timeline.