Access issues

Users occasionally lose access to Opsflw Connect services after role changes or network adjustments. Follow the collapsible checks below to restore access while maintaining security controls.

Validate account status

Confirm the user exists in the identity provider and is mapped to the correct Opsflw Connect role.

opsflowctl iam user get --email user@example.com

If the account shows as suspended, reinstate the user in the identity provider and re-run the command to confirm the change propagated.

Review recent role assignments

Audit the permissions granted to the user to ensure they cover the requested resource. Compare the existing role with the entitlement matrix in the platform runbook.

opsflowctl iam role assignment list --user user@example.com

When a role is missing, reapply the mapping and document the adjustment in the change management system.

Check for network restrictions

Access issues can also stem from network policy updates. Validate that the user's source IP range is still allowed through the relevant firewall rules or VPN configuration. Coordinate with the networking team if changes are required.