Issue Summary

When a Jira Cloud administrator uses "Log in as user" (impersonation) to validate a user's experience, workflow step properties are not enforced against the impersonated user's identity. The impersonation flow can evaluate license and session checks against the admin's identity while evaluating permission checks against the impersonated user, causing workflow-based restrictions (e.g., jira.permission.edit.group, jira.permission.comment.denied) to fall through.

Expected Results

• "Log in as user" should provide a fully permission-accurate session, including enforcement of workflow step properties, so administrators can validate workflow restrictions before going live without requiring end-user involvement or dedicated test accounts.

Actual Results

• Impersonation validates: project visibility, issue visibility, issue security levels, and general navigation.

• Impersonation does not accurately replicate: jira.permission.* workflow step property enforcement based on group membership, project role, or user identity.

 h3. Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available