When an organization administrator accesses a workspace, their org-level admin privileges override the more restrictive workspace-level role assignment (e.g.,
Launch-only
).
This makes it impossible to test role-based access control using admin accounts and can lead to unintended access to workspace resources.
The platform should respect workspace-level role assignments even for org admins, or provide a mechanism to "step down" to test restricted roles without requiring a separate user account.