I’ve read all the guidance above but I don’t understand the logic behind the permissions setup:
It seems that for many positions, ASM, Unit Activities coordinator etc, the permissions must be actively turned on for their core functions (advancement for an ASM, create activities for a Unit outdoor coordinator). Is this intentional? If we assign a volunteer to a role, my preference is that they start with the permissions necessary to do the role.
@PeterSymonds the main point is you are applying your unit’s - unit maintenance globally. Not all units have ASM do advancements, Some only have SMs or UACs do it. Some units have UACs do Advancement, some UACs just go to the Scoutshop.
Other than the Key 3, there are very few roles that units all use in the same way. This is why it was setup so units could individualize.
SUAC does hope we can get to where Troop 333 - can say I want all T333 ASM to have these permissions, and save it internally. So then a new T333 ASM is registered they have the T333 ASM Permissions. That is in our backlog but has hurdles that prevent it right now.
I recognize that units do things differently but I think the default to no permissions is incorrect.
I also recognize that I probably am falling on deaf ears here, but I’ve been dead in the water on tasks I’ve been asked to do for months.
I hope you don’t take my frustration personally.
thanks,
I think it’s more precise to say that the SUAC volunteers are in the position that they aren’t directing the development, and can only explain what was implemented. The decisions regarding what the default permissions are was made by national. It sounds like there’s a story already out there with development to allow units to set defaults, based on Donovan’s post.
You might be able to further push for a change to the defaults (as opposed to just the persistence of unit “presets” described by Donovan) via your council professional staff, explaining why the defaults should be changed and how the existing defaults impact unit operations (or deviate from the operations withing Guide to Advancement, to the extent that you believe they do).
Thanks for the perspective.
@PeterSymonds
The default permissions align with the Guide to Advancement as much as possible. The GTA says it is the Unit Leader (Scoutmaster) that is responsible for all advancement. The Scoutmaster must authorize others to sign off on advancement. This is handled in Scoutbook Plus by the default permissions. If the Scoutmaster wants to allow others to sign off on advancement, then a unit Key 3 or Key 3 Delegate can add those permissions.