Who can do what: Roles and permissions
Use this reference to match Woggle access to a person’s real job. A Unit role sets the baseline, while Unit settings, audiences, Household relationships, and Event or Channel responsibilities can narrow what that person can do.
Start with the four Unit roles
Section titled “Start with the four Unit roles”These are the canonical Unit roles in Woggle. A person may hold more than one role in a Unit.
| Unit role | Baseline access |
|---|---|
| Unit Admin | Unit settings, roles, Invites, roster management, Groups, Channels, Events, Announcements, eligible RSVP and volunteer actions, audit history, and report review |
| Leader | Roster and audit-history view, Groups, Channels, Events, Announcements, eligible RSVP and volunteer actions |
| Parent/Guardian | Group and roster view, eligible Channels, Household RSVP, eligible adult volunteer roles, and personal notification settings |
| Youth Member | Group and roster view, eligible Channels, eligible RSVP, and personal notification settings |
Baseline access is only the first gate. Unit settings can narrow Invites, roster visibility, Group creation, and Event management. Audience, membership, Household, and lifecycle checks still apply.
Compare access by area
Section titled “Compare access by area”Use this matrix for current product access. “View” always means the person must also belong to the relevant Unit, Group, Channel, Event audience, or Household context.
| Area | Unit Admin | Leader | Parent/Guardian | Youth Member |
|---|---|---|---|---|
| Unit settings and roles | Manage Unit settings and Unit roles | No baseline management access | No baseline management access | No baseline management access |
| Invites | Create, view, and manage | Create only when Unit Invite settings allow it | Create only when Unit Invite settings allow it | Cannot create |
| Roster | View, change roles, and remove members | View; Unit settings can limit the roster to assigned Groups | View, subject to Unit settings | View, subject to Unit settings |
| Groups | Create, manage, view, and review joins, subject to Unit settings | Create, manage, view, and review joins, subject to Unit settings | View and request to join when the Group permits it | View and request to join when the Group permits it |
| Channels and messages | Create and manage Channels; read or post when eligible | Create and manage Channels; read or post when eligible | Read or post as an audience member; Guardian-only visibility is read-only | Read or post when eligible and youth posting is on |
| Events | Create, edit, or cancel when settings and Event state allow | Create, edit, or cancel when settings and Event state allow | RSVP and claim an eligible adult volunteer role | RSVP when eligible; no baseline volunteer access |
| Announcements | Create and manage; read or acknowledge when targeted | Create and manage; read or acknowledge when targeted | Read or acknowledge when targeted | Read or acknowledge when targeted |
The Announcement guide shows one task where Unit Admin and Leader access is the same. Other areas can use different Unit settings, so do not carry that result into a different row.
Keep narrower responsibilities separate
Section titled “Keep narrower responsibilities separate”Several labels describe a relationship or responsibility instead of a Unit role:
- Household Guardian and Household Youth are Household relationships. A Guardian can manage Household membership and eligible Youth profiles. A Youth Household member cannot manage the Household.
- An Event organizer is responsible for a specific Event. The organizer must be an active Unit Admin or Leader. A Unit Admin can reassign the organizer; Event permissions, Unit settings, audience, and Event state still apply.
- A Channel leader can manage that Channel. This responsibility is stored on the Channel and does not change the person’s Unit role.
- A Group member or Channel participant receives only the audience access attached to that Group or Channel. Participation does not grant Unit-wide settings or roster management.
- A volunteer role is an Event job. Claiming one does not grant Event editing or Unit administration.
This distinction keeps one Event, Channel, or volunteer assignment from turning into permanent Unit-wide access.
1. Review the Unit controls
Section titled “1. Review the Unit controls”Open Roles & Permissions from Unit settings. Review the setting tied to the person’s job, not every available control.

This screen includes product labels such as “always enforced” and “youth safe.” Treat those as interface labels, not proof of a policy guarantee. Review Event, Channel, Group, and Household access in its own context.
Choose the smallest role that covers the recurring job:
- Use Parent/Guardian for family RSVP, eligible adult volunteering, and standard member participation.
- Use Leader for recurring Unit-wide Group, Channel, Event, or Announcement management. For a job limited to one Channel, use the Channel leader responsibility without changing the person’s Unit role.
- Use Unit Admin when the person must manage Unit settings, roles, Invites, or the roster.
2. Change a member’s Unit roles
Section titled “2. Change a member’s Unit roles”Open Roster, choose the member, and select Edit roles. Turn on only the verified Unit roles that match the person’s work, then select Save.
Woggle rejects adult Unit roles for a Youth Member. It also blocks a role change that would leave the Unit without a Unit Admin.

In this seeded record, Unit Leader maps to the Leader role. Event Manager is a narrower Event responsibility, not another Unit role. Group assignments are separate access decisions.
3. Review Event, Channel, Group, and Household context
Section titled “3. Review Event, Channel, Group, and Household context”A Unit role change does not replace these checks:
- Open each assigned Group and confirm the member belongs to the intended audience.
- Open each relevant Channel and review its leaders and members. Keep at least one Channel leader.
- Open the relevant Event and confirm the organizer and audience. Use a volunteer role for an Event job that does not require editing the Event.
- Open the Household separately when the change affects a Guardian, a Youth profile, or family RSVP context.
4. Confirm or remove access
Section titled “4. Confirm or remove access”After a role change, reopen the member record and confirm the saved Unit roles. If the person manages a Channel or Event, check that object separately. A Unit Admin or Leader with audit access can also review Recent changes.
To remove Unit-wide access, clear the unnecessary Unit role and save. Removing a person from the roster is a broader action: it removes that Unit membership, its roles and permissions, and its Group memberships. Woggle protects the last Unit Admin from either action.
Guardian visibility and policy boundaries
Section titled “Guardian visibility and policy boundaries”Guardian visibility is verified for a Youth Member’s Household profile, eligible Event context, and private Channels that contain that Youth. That is narrower than a promise of visibility across every screen or communication path.
These role settings do not show a direct-message restriction. No current direct-message workflow is verified.
For eligibility, consent, privacy, reporting, and safeguarding policy, use Woggle’s official Youth Suitability and Child Safety Standards pages. Keep Unit access decisions aligned with the rules that apply to your organization.
Thanks. Your feedback helps us keep this page useful.