Squad captains
How group-scoped roles let a captain manage their own squad - lineups, attendance and members - without club-wide access.
A squad captain is a coach with limited reach. They run their own squad - seating crews, taking attendance, managing their members - but can't touch the rest of the club. Rowbot does this with group-scoped roles.
How scope works
A role is a bundle of permissions. What changes for a captain is where those permissions apply:
- A club-wide role applies everywhere - the head coach can schedule and seat for any squad.
- A group-scoped role applies to one squad only. Grant someone a "Squad Captain" role within a group and they can manage lineups, attendance and members for that group, and nothing else.
So the same set of capabilities - build a lineup, take the register, manage the people - behaves differently depending on the scope it's granted in. A captain seating their own squad works exactly as in Building lineups; they simply can't see or touch boats and members outside their group.
Captains can also gain permissions through a position within a group - for example the person holding the squad's "Captain" position inherits its permissions for that group automatically.
Making someone a squad captain
This is set up by a club admin, not the captain themselves. In short: pick the person, grant them the captain role, and scope it to their squad. The admin guide walks through the exact screens.
If a captain reports they "can't see" a session, crew or member, it's almost always because the item belongs to a different group than the one their role is scoped to - that's the scoping working as intended, not a bug. Widen their scope (or grant a second group) only if they genuinely need it.
Learn more
Roles & permissions (concept)
The model behind roles, scopes, groups and positions across the platform.
Managing roles & permissions
The admin steps to create roles and grant them club-wide or scoped to a squad.