Skip to content
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

tiered permission model #39

Closed
bobheadxi opened this issue Oct 8, 2018 · 2 comments
Closed

tiered permission model #39

bobheadxi opened this issue Oct 8, 2018 · 2 comments
Labels
theme:feature Request a new feature.

Comments

@bobheadxi
Copy link
Member

The current Rocket only has admins and everyone else - it's probably more flexible to have an additional lead position that has permissions like team and repo creation. Something like:

  • admin: create, delete, read
  • lead: create, read
  • everyone else: read
@bobheadxi bobheadxi added the theme:feature Request a new feature. label Oct 8, 2018
@rwblickhan rwblickhan added this to Backlog in Rocket 2 Planning via automation Oct 8, 2018
@rwblickhan
Copy link
Collaborator

This is part of our roadmap (in fact if you look at permissions.py you'll see that TEAM_LEAD is one of the three possible permissions levels) though I'm noticing a bit of confusion about that - I didn't explicitly write it down in our docs, so I may update those at some point (and close this when I do).

@rwblickhan
Copy link
Collaborator

This is already part of our data model and included more specifically in other tickets; closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme:feature Request a new feature.
Projects
Development

No branches or pull requests

2 participants