Skip to content
This repository has been archived by the owner on Oct 6, 2022. It is now read-only.

Support for Groups/Teams #180

Open
tombuildsstuff opened this issue Sep 18, 2016 · 2 comments
Open

Support for Groups/Teams #180

tombuildsstuff opened this issue Sep 18, 2016 · 2 comments

Comments

@tombuildsstuff
Copy link
Contributor

We've got certain groups of users who need to be able to access every project - our example is our Operations Team. Right now - we've got to add each member manually to each project, which is.. less than optimal.

Instead of assigning by emails to a particular project - I was thinking that some kind of Group assignment could work - ideally pulling from the SSO provider? Alternatively this could be group-assignments from within Hobknob.

Permissions for Groups could then be assigned in much the same way as users are via emails right now?

Thoughts?

@ryantomlinson
Copy link
Contributor

Love this idea @tombuildsstuff . Are you thinking of granular permissions too? e.g. "Can Create", "Can Toggle" or keeping it simple with "ReadOnly" and "Admin"?

@tombuildsstuff
Copy link
Contributor Author

@ryantomlinson I don't see any point having beyond 'ReadOnly' (default)/'ReadWrite'/'Admin'?

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

No branches or pull requests

2 participants