-
Notifications
You must be signed in to change notification settings - Fork 14
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
Team Management #251
Comments
I think that being able to add people to a team role should be a seperate permission. That way you can give it to the trustee role, but also give it out as needed. Some teams would make sense to allow 1 or 2 of the existing team members to allow new team members, but for others it might not make much sense. |
Hmm interesting idea
`role.team.add.all`
`role.team.remove.all`
`role.team.approveRemoval.all`
`role.team.add.membership`
`role.team.remove.membership`
`role.team.approveRemoval.membership`
`role.team.add.metalworking`
`role.team.remove.metalworking`
`role.team.approveRemoval.metalworking`
Something like that?
Would need to generate these on the fly when creating new teams
Matt
… On 30 Aug 2017, at 14:42, James Hayward ***@***.***> wrote:
I think that being able to add people to a team role should be a seperate permission. That way you can give it to the trustee role, but also give it out as needed.
Some teams would make sense to allow 1 or 2 of the existing team members to allow new team members, but for others it might not make much sense.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#251 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOT3AmYsyMAf3iqNs6RD1v8_LRLU4Apks5sdWa4gaJpZM4PHMKE>.
|
I was more thinking of just having a general:
etc, and making a role called something like |
Mind we don’t assigned permissions to users, so to limit adding or approval to just some members of a team would be a pain
Matt
… On 30 Aug 2017, at 14:42, James Hayward ***@***.***> wrote:
I think that being able to add people to a team role should be a seperate permission. That way you can give it to the trustee role, but also give it out as needed.
Some teams would make sense to allow 1 or 2 of the existing team members to allow new team members, but for others it might not make much sense.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#251 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOT3AmYsyMAf3iqNs6RD1v8_LRLU4Apks5sdWa4gaJpZM4PHMKE>.
|
It would be manual, absolutely. That might be a good idea... |
I'd suggest not allowing the "apply to join team" option, under the same logic as we require prospective members to visit the space and talk with one of the membership team before they can start the signup process. Currently the membership team have the ability to add other members to the membership groups on HMS, I'd consider a similar approach of "any existing team member has the ability to add a new team member", but create and document a more solid role description for each team and joining process. I plan on updating all the team pages on the Wiki, so I'll look into this? |
closed via #400 |
Need to work out how we deal with adding and removing team roles to users, (this should be the preferred way rather than #250 )
The text was updated successfully, but these errors were encountered: