Skip to content

Create designs for creating custom roles based on permission buckets #457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jaaydenh opened this issue Mar 5, 2025 · 3 comments
Open

Comments

@jaaydenh
Copy link

jaaydenh commented Mar 5, 2025

Currently custom roles are assigned by choosing a set of granular permissions individually. The proposed design should allow users to define custom roles based on permission buckets as discussed here, https://www.notion.so/coderhq/Permissions-and-Deployment-Settings-1add579be592809a9af2ed352b00a29f

@jaaydenh jaaydenh self-assigned this Mar 5, 2025
@jaaydenh
Copy link
Author

jaaydenh commented Mar 14, 2025

Option 1

Permission buckets

  • Allow users to turn on/off the full set of permissions for the defined permission buckets
  • Using the switches is all or nothing meaning it adds or removes all the permissions defined by the bucket.
  • avoids the situation where a user may not have the entire set of necessary permissions which can happen when setting granular permissions.
  • The granular permissions will get visibly toggled on/off in the permissions table below when the switches are flipped.
  • Question: should the roles page where the current list of custom roles is view, still only show the granular permissions for each role, or should all call out when a bucket of permissions is applied to a role?
Image

@jaaydenh
Copy link
Author

jaaydenh commented Mar 14, 2025

Option 2

Separate tabs
Tab A - current custom role create page for the granular permissions
Tab B - exact same design as status quo except the permissions checkbox table only has the permissions buckets and under each bucket is the granular set of permissions checkboxes that apply to that bucket

  • This would allow a user to clearly see what granular permissions apply to each bucket.
  • Need to decide if buckets or granular permissions should be the first tab and therefore more obvious to the user
  • Questions: should buckets still be all or nothing or could a user remove specific permissions from a bucket for a custom role?
Image

@jaaydenh
Copy link
Author

@Kira-Pilot @stirby here are 2 design options for the permissions bucket idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant