How-to guide
Section permissions
A Section Team Leader runs their own section. Another section's young people, events and register stay with that section's leaders.
Watch this on its own pageEverything in their own section
A leader of Beavers, and nothing else in the group, can add an event, add a young person and take the register in Beavers, and see the young people there.
They can edit, publish and unpublish their own section's events, and add new ones for their sections. An event for the whole group is a Group Lead Volunteer's to add.
Young People lists only the young people in their sections, a term's plan shows only their sections' meetings and events (plus anything for the whole group), and with section stock turned on, Badge Stock shows only the badges for their sections and the stock they hold.
For the young people in their sections they can also edit the record, add emergency contacts and consents, link parents, award badges and sign off requirements, see their invoices, and move them up to the next section. They can change their section's details, like its meeting night, post announcements to it, and record the adults who helped at its events.
They run their section's waiting list, offering places to families waiting for their kind of section, and see its size planning. They can add to the group's programme activity library, and see and keep the custom records for their own young people.
Messages are limited to their own section too: they email and message the families in their sections (or at their sections' events), see the messages they sent, and see inbox messages from their own families. They can't message the whole group.
Not another section's
Another section's events don't open for them at all: the Scouts' register shows Event not found. Taking attendance, adding young people and creating events stay with the leaders of that section.
The group's money isn't theirs to see either: Finance doesn't appear in their menu. They still see the money for their own section's events, on the event's Budget tab.
Giving someone more
To let someone help in two sections, give them a role in each from Team. Group-wide roles, like the Group Lead Volunteer, cover every section. Roles and permissions covers the rest.
Some things stay with the Group Lead Volunteer and the group's other leaders: closing a section, term dates, announcements and messages to the whole group, message templates, the trustee documents, and subject access requests and data breaches.
To take an area away instead, like building maintenance for an assistant leader, set it to No access in Team → Permissions. Roles and permissions explains what that does.
Setup
More in this topic
Districts, WordPress, importing from your old system, SSO, the API, privacy mode, and the assistant.