Roles and Navigation

Use this page when the main question is how access usually maps to the major workspaces in SyncReserve.

Typical role shape

Owner

Usually the broadest administrative role, with visibility across operations, commercial controls, reporting, and governance.

Manager

Usually broad operational and commercial access, but often with less governance authority than an owner.

Staff

Usually concentrated in day-to-day operating work such as bookings, service activity, and selected customer workflows.

Coach

Usually centered on coaching, programs, or delivery-specific work rather than broad platform governance.

Role is a strong hint, but not a complete prediction.

In practice, navigation can also vary by:

tenant business model
enabled modules
commercial entitlement
location or org structure

That means the right mental model is "typical access pattern," not "universal rule."

For platform integrations, Owners and Managers now use Settings > Developers (/admin/settings/developers). That workspace is commercial-gated behind the platform.api module and is not available to Staff or Coach roles.

Why this matters in public docs

This page exists so evaluators can understand that SyncReserve supports differentiated operating roles.

That is important because a serious club platform should not assume that owners, managers, front-desk staff, and coaches all work in the same way or need the same controls.

What this page is not

This page is a reference summary.

It is not:

a complete permissions matrix
a security specification
a hidden list of route-level restrictions

/docs/overview/admin-navigation
/docs/settings/settings-overview
/docs/reference/developers-workspace