12 Feb 2020 | improvement
Changes to captain and vice-captain permission settings
In response to feedback, we recently updated the SupporterBase permission sets to distinguish more clearly between the roles of captain and vice-captain, and to support a higher level of group autonomy and independence.
In short, as part of this update, vice-captains assumed most of the same permissions as captains previously enjoyed, while captains assumed many of the permissions only previously afforded to admins but solely for their own particular group(s).
More specifically, we have:
- Upgraded the captain access level so they’re able to send out bulk communications and create events without approval from admins, as well as approve bulk communications and events drafted by vice-captains.
- Importantly, the ability to add new group captains will still be restricted to admins. Captains can initiate this process but admin approval is required for a new captain to be actually granted access. Indeed, admins are still the only access level able to manage other users in general.
- Upgraded the vice-captain level so they’re able to create bulk communications and events, but still need approval before sending/publishing (essentially similar to what captains could do previously).
- Vice-captains will still be able to handle one-on-one communications without approval via email, SMS and phone calls (including call lists).
- Configured notifications to be sent to group captains as well as admin point people (if any are configured for the group) when vice-captains create new events or bulk communications that are awaiting approval.
- Admins and captains are always able to opt-out of notifications on an individual basis. This can be done by clicking “Update profile” and deselecting the “Receive notifications” checkbox.
Please review the following page for a full overview of permission and approval settings for supporter group actions: https://www.supporterbase.com/access_levels