Platform overview
One platform for how a gym actually runs
Gymciety organises gym operations into one tenant-isolated platform: staff work in the admin panel, members use a separate portal, and every module respects the same roles, isolation and audit rules.
How it's organised
Not every module is production-live for every tenant. What each gym sees depends on what has been enabled for it — and several capabilities are still pilot or planned (see Features).
Tenant-isolated administration
Each gym is its own tenant. Tenant context fails closed, so a query with no tenant returns nothing — one gym can never see another's data.
Staff roles & permissions
Owners, managers, front desk, coaches and other roles get exactly the access their role allows, enforced at both the page and action layers.
Member operations
Member records, membership plans and agreements, notes and activity — with plan prices recorded as information, not billed automatically.
Scheduling & attendance
Class types and sessions, one capacity-safe booking path with waitlists, and front-desk or self check-in with eligibility rules.
CRM & lead operations
Capture leads, move them through a pipeline, and track follow-up tasks and notes — internal records only, no external CRM connected.
Staff operations
Staff profiles, scheduling and availability, an internal time clock and timesheet summaries — internal time-tracking, not payroll filing.
POS & inventory groundwork
Product and inventory record-keeping exists as groundwork. Taking payments at a point of sale is not live.
Reporting & analytics
Owner and coach dashboards for bookings, attendance and operations, with PII-free CSV exports and opt-in in-app digests.
Controlled rollout & auditability
Capabilities are turned on deliberately, and sensitive actions are recorded in an append-only audit trail.