# Roles, relationships and permissions

Understand why different people see different tools.

Type: Reference

For: All members and academy owners

Before you start: Permissions are academy-specific and may be combined or restricted by scope.

Reviewed: 2026-09-16

## Role guide



| Role or relationship | Typical access |
| --- | --- |
| Owner / operations administrator | Academy operations and management, according to the granted role. |
| Finance administrator | Authorised fee, payment and finance workflows; does not imply every operational permission. |
| Head coach / coach / assistant | Assigned coaching work and relevant participant/session scope. |
| Guardian | Permitted records for verified linked participants. |
| Player | Permitted personal schedule, programme and academy records. |
| Staff | Own permitted payslips, expense claims and notices; not general people or attendance access. |

## Three checks apply together

A role identifies responsibility. Scope identifies the groups or people the role applies to. Entitlement identifies the modules the academy's plan includes. A visible role switch is a navigation aid, not a way to override these checks.

Pickup authorisation and explicit care permission add separate checks. A guardian relationship does not by itself establish pickup authority. Owners should review role and relationship changes carefully, particularly when someone leaves the academy.

## Related guides

- [Protect your account and manage access](https://kelab.app/docs/security.md)
- [Manage participants and guardian relationships](https://kelab.app/docs/people-guardians.md)
- [Record care, arrival and authorised pickup](https://kelab.app/docs/care-pickup.md)
- [Plans and included modules](https://kelab.app/docs/plans-limits.md)