You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actual result: an error form with the below messages
This is 'fixable' by allocating the 'Organization User Admin' to user2. We don't document this Role in the docs pages, can somebody confirm what is the appropriate 'Coder way' to enable a user, and how/why adding ALL permissions (except three dormant ones that cannot be added to a Custom role) does still not allow the new Role privileges to read the org users?
Relevant Log Output
"user" must be an existing uuid or username
queried user="user1"
Expected Behavior
Expected result: user2 is able to see the details of workspace1 and navigate to all coder apps defined in workspace1
Steps to Reproduce
Have user1 with the role of Member create a workspace (let's say workspace1)
Create a role "Support" and give the role all available permissions (in the end we want to scope this down to the must have permissions for accessing someone else's workspace - but for simplicity sake let's just assign everything)
Assign the Support role to user2
user2 lists all workspaces in the environment and clicks on workspace1
Environment
Host OS:
Coder version:
Additional Context
No response
The text was updated successfully, but these errors were encountered:
ericpaulsen
changed the title
bug: custom role permission allowing admin access to user workspaces fails when accessing workspace on behalf of user
bug: failure when admins access workspaces on behalf of users
May 6, 2025
@ericpaulsen can you reproduce this on main? I am able to open another workspace page from a second member. The member has no site wide roles, just custom roles.
…7707)
Closes#17691
`ExtractOrganizationMembersParam` will allow fetching a user with only
organization permissions. If the user belongs to 0 orgs, then the user "does not exist"
from an org perspective. But if you are a site-wide admin, then the user does exist.
Is there an existing issue for this?
Current Behavior
Actual result: an error form with the below messages
This is 'fixable' by allocating the 'Organization User Admin' to user2. We don't document this Role in the docs pages, can somebody confirm what is the appropriate 'Coder way' to enable a user, and how/why adding ALL permissions (except three dormant ones that cannot be added to a Custom role) does still not allow the new Role privileges to read the org users?
Relevant Log Output
Expected Behavior
Expected result: user2 is able to see the details of workspace1 and navigate to all coder apps defined in workspace1
Steps to Reproduce
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: