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

New user role between Staff and Liaison #352

Open
inghamn opened this issue Mar 26, 2024 · 2 comments
Open

New user role between Staff and Liaison #352

inghamn opened this issue Mar 26, 2024 · 2 comments
Assignees

Comments

@inghamn
Copy link
Member

inghamn commented Mar 26, 2024

There seems to be a need to have a user role that can edit committee information and manage membership for all committees, but without permission to alter the seats and terms.

Setting up the seats and terms is something that needs to be done carefully and must conform with municipal code.

@inghamn inghamn added this to the 2.7.1 milestone Mar 26, 2024
@inghamn
Copy link
Member Author

inghamn commented Mar 27, 2024

The consensus among city staff has been that Liaisons should not be the people who appoint board members. It sounds like there should be a role for something like "Appointers". These people would manage board membership as well as make sure seats and terms were set up correctly.

The "Appointer" role might need to be department based. I don't think we want to manage "Appointers" for every board and commission.

@inghamn inghamn changed the title User role between Staff and Liaison New user role between Staff and Liaison Mar 28, 2024
@inghamn inghamn self-assigned this Sep 19, 2024
@rbdietz
Copy link
Member

rbdietz commented Sep 26, 2024

Setting up seats can and probably should be an administrator role. This is very rare and needs to be done correctly.

Appointers have been 1-2 people in OOTM and Council/Clerks office, adding new appointees made by OOTM or Council. This shouldn't be a role for every department.

Board setup/config are different from appointing people.

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

2 participants