What Youth Leaders Can and Cannot See

Scouting is youth-led, and MySummitKeep is built for that. When a Scout holds a position of responsibility — Senior Patrol Leader, Patrol Leader, Crew President, Boatswain, and the like — they get real tools to run the program: they can open registrations, take roll, hand out tasks and event roles, and keep the schedule. What they never get is other people’s private information. This page spells out where that line sits so nobody is surprised by a missing tab or button.

What youth officers can do

A youth officer’s position grants the Event.Manage permission (alongside the everyday member permissions), which lets them run the logistics of an event end to end:

• Registrations — see who has RSVP’d and their status, add a member to an event, and approve or reject a pending registration.
• Attendance — take roll on the Attendance tab or the event roster, mark present / absent / excused, and use Mark All Present. See Recording & Reviewing Attendance.
• Event logistics — tasks, event roles, the schedule, packing lists, meal assignments, and meeting notes.
• Leadership Council — the PLC workspace, its 30 and 90 day plans, and the council channel. See Patrols, Dens & Divisions.

Nothing here changed with the tightening described below. If your SPL ran registrations last month, they still can.

Youth officers can run roll call in Camp Mode, but they see no Sign Off button there: adult requirement sign-off, with or without a signal, is adult-only. A separate troop setting can let qualifying Scouts sign off other Scouts’ Scout through First Class requirements from the Scout Rank Progress page; see Letting Scouts Sign Off Requirements. See Camp Mode — Working Without a Signal.

What youth officers cannot do: reach adults

A youth officer’s Event.Manage does not include anything that emails or charges an adult. Those actions need the adult-only Event.AdultOutreach permission, held by Scoutmasters, Assistant Scoutmasters and unit admins and stripped from every youth account. A youth officer is refused, with no approval step, on:

• Message Attendees (the event-wide message)
• Invite a Visitor (emails an outside adult an RSVP link)
• Reminders (configuring the reminder emails sent to guests)
• Removing a guest (sends a removal email and can issue a refund)
• Emailing the event packet (sends the participant packet to registrants and their parents)
• Inviting leaders to an event (notifies adult leaders)

Ask an adult leader to do these; everything else in the list above still works for your youth.

What youth officers cannot see

Anything that is somebody’s contact or health detail is an adult-leader-only read. Two permissions cover it, and both are stripped from every youth account automatically — no matter what position they hold or what role a unit admin assigns them:

Permission	What it unlocks	Who holds it
Event.ViewGuests	The Guests tab on an event (non-member guest RSVPs with names and email addresses), its Export CSV, and the Unit Prospects page of guests who opted in to hear from you.	Scoutmasters, Assistant Scoutmasters, and unit admins
Event.ViewAttendeePii	The Emergency Contacts export on an event, the unit-wide standing permission-slip list, the Camp Mode Paper Backup (trip pack PDF) and its per-member emergency contact and AHMR badges, the Trek/Voyage Emergency Plan, AHMR eligibility, and Packet download, and the special-needs and transportation notes on individual registrations (dietary restrictions stay visible — see below).	Scoutmasters, Assistant Scoutmasters, and unit admins

In practice a youth officer will notice:

• No Guests tab on an event, even when guest RSVPs are turned on. A ?tab=guests link someone forwards them simply opens the event on the first section they can see.
• No Emergency Contacts button on the Registrations tab. They still see the roster, but Message Attendees is not offered (see above).
• The Dietary tab in Meals & Catering stays visible. Dietary restrictions and allergy warnings are need-to-know for whoever plans and cooks a meal, youth officers and patrol members included. Medical notes, special needs and transportation notes are not — those stay with adult leaders.
• Camp Mode roster cards show no emergency contact or AHMR badge for them — a note that these details belong to adult leaders takes their place. Roll call there still works, and there is no Paper backup button.
• No Trek or Voyage Emergency Plan, AHMR eligibility check, or Packet download — those stay with adult leaders; the rest of trek/voyage planning remains open to them.
• The standing Permission Slips page does not show the unit-wide list or its “members without a slip” banner; an adult leader checks whether a Scout’s slip is on file.
• Unit Prospects shows an access-denied notice instead of the list, and the entry is not offered in their sidebar.

Why the split?

Guest and prospect lists are the personal details of adults who are not members of your unit, and emergency contacts and health notes are the most sensitive records a unit keeps. Both belong with the registered adult leaders who are accountable for them under Scouting America’s Youth Protection standards. Splitting these reads out of Event.Manage lets your youth keep leading without handing a fourteen-year-old a spreadsheet of parents’ phone numbers.

Who holds the adult-only permissions

The two permissions above are part of the Scoutmaster and Assistant Scoutmaster role sets, and unit admins inherit the Scoutmaster set. Committee chairs and other adults who sit at the leader tier get them through the same role sets. If an adult leader is missing one of these surfaces, a unit admin can check their role from the member’s profile — see Unit Settings for the roles and permissions page.

If a youth officer needs a guest list or an emergency sheet for an outing, an adult leader pulls it. That is the intended workflow, not a gap.

Related

• Event Planning — the event workspace and its tabs.
• Recording & Reviewing Attendance — taking roll.
• Health & Safety — emergency contacts and health forms.