Features
Staff & Role Permissions
The reason an owner can let the front desk use the system without showing them what the gym earns.
Access
Roles you build, not three you are given
A trainer needs members and attendance. A manager needs those plus invoices. Nobody except the owner needs profit and loss. Rather than three fixed roles that never quite fit, permissions are individual and a role is a set of them.
- View, create, edit and delete as separate grants per module
- Roles are per gym, so one gym's "Manager" is not another's
- The menu a person sees is built from what they can actually reach
Enforced where it counts
Hiding a button is presentation. Every permission here is also enforced by row-level security in the database, so a person without the revenue permission cannot read revenue -- not through the interface, and not by any other route either.
That distinction matters most for the thing owners actually worry about: a staff member who leaves, or a trainer who is curious about what the gym takes.
More than one gym, one login
An owner with several branches switches between them from the header rather than keeping a password per gym. Each branch's members, invoices and staff belong to that branch and are not visible from another -- enforced in the database, not by filtering a shared list.
Access is granted two ways, because they answer different questions. A named person can be given a role at a second gym, which covers the manager who works across two sites. Separately, a gym can be attached to a parent, which gives that parent's administrators access without a record for every person at every branch.
Also in operations
- Staff records
- Who works here, their role, and their contact details.
- Coaches
- Trainers, their specialities, and the members assigned to them.
- Staff leave
- Requests, approvals and a leave history per person.
- Staff attendance
- Recorded like member attendance, including from the same devices.
- Inventory
- Equipment and stock, with sellable items priced so they can go on an invoice.
What this does not do
Worth knowing before you book a call, not after.
- There is no per-record sharing. Permissions are per module and per gym, not "this trainer sees only these fifteen members".
- No audit log of who changed what. The system records who created a payment or a member, not a full change history.
- Staff do not clock in and out for payroll; staff attendance is a record, not a timesheet that produces wages.
- Chains are one level deep -- a branch cannot itself have branches -- and reporting is per gym, so a consolidated view across every branch is not available yet.
If one of these matters to you, say so on the call. Tell us what you need and we will give you a straight answer about whether it is coming.
Questions we get asked
You get help from the people who build the product rather than a ticket queue. Setup and data import are done with you on a call, and you can reach us by email afterwards at gymnexuscrm@gmail.com.
Most gyms are running within a few days. The work is mainly getting your existing member list in and setting up your plans; we do the import with you on a call rather than handing you a spreadsheet template and wishing you luck. You can start using it for new members immediately and move historical data over as you go.
Works with
See it with your own data
A short call, your actual member list, and an honest answer on whether this fits how you run the place.
We will talk through your gym and what it would cost, on one short call.