Give activity co-leaders automatic permisson to see rosters
Currently it is apparently necessary for a co-leader to be made an activity admin or a committee admin in order to see the roster for that activity, adding another step for the primary leader. Can we not remove extra keystrokes here for our busy volunteers? If we make someone a co-leader we trust them to do everything we would do as a leader.
First, anyone who is to be a co-leader should already be on a committee roster (any committee roster as a leader) whcih means they could easily be the Primary Leader. Why would this ever not be the case?
Second, anyone on a roster may view and mange the “team roster,” the one that that is accessed from the "Manage Activity " portlet or “Roster” in the Admin Panel, if the “Admins” box in their activity roster record is checked.
So the only added step for adding a co-leader to an activity roster is to check the “Admins” box. This is the first field after looking up the person being added and has help text explaining why this box might be checked. Checking a box, one click, does not seem overly burdensome, especially in light of the many other needs and desires for our website.
Thanks for the comment, Josh! You are correct that we have several different leader permissions, but from the permissions perspective, they are all different from each other. The two driving forces for the design we have are (1) flexibility, and (2) giving primary leader full control of their activity. The "admins" checkbox on roster records allows the primary leader this flexibility and control. If they want another leader to be able to mange the activity details and roster, they need only check the "Admins" box for that person's roster record and choose whatever role is appropriate (co-leader, mentored leader, assistant leader, or instructor).
With respect to mentoring new leaders, there are options and a few things to consider: https://www.mountaineers.org/volunteer/schedule-manage/activities#mentoring-new-leaders.
I hope this added explanation helps.
Joshua Stein commented
Jeff, I'd like to add an additional perspective to this.
I was mentoring a hike, the first I've done, and as part of the process I was supposed to be made a co-leader. I was confused that I was unable to see the roster for the activity since I was unaware of the admin checkbox you mentioned (now I know). One issue I think Cheryl is highlighting here is that we have leaders, co-leaders, assistant leaders, and mentored leaders. From a permissions perspective, none of them are different from each other which I think is unintuitive.
An RBAC approach would likely be the most intuitive since one would easily be able to understand the following:
- Primary leader = full permissions (edit route, roster, close activity)
- Co-leader = most permissions (edit roster?)
- Assistant leader = few permissions (view roster?)
- Mentored leader = ??? (I've never seen this used)