Cross-location access and visitor hours
A member stays a member of their home branch and is simply hosted elsewhere: no second membership, nothing charged to them, every visit recorded at the host. The home branch owes the host an agreed fee per visit, capped per member per month, and the monthly settlement lands in Accounts. The member's own plan rules travel with them — an off-peak plan is still off-peak at every branch — and each host branch can add its own visitor hours on top, so a branch that only admits men from 15:00 keeps that rule for visitors too.
What you'll do
Switch the network on, choose which branches host and which members roam, set the visit fees, and set each branch's visitor hours.
You'll need: to be the organisation owner (or an HQ observer). Branches must already exist under the organisation.
Steps
-
Open Settings → Organisation → Cross-location access. Turn on Cross-location access enabled — the master switch for the whole network.
-
Set the Agreement currency (what the deal is priced in — a branch's books currency or a neutral one like USD), the Monthly cap / member (network total per member per month; blank for none) and how amounts convert into each host's books: Host live rate or a Fixed rate per branch pair.
-
Under Branches, for each branch decide: Hosts visitors from other branches (it accepts visitors), Its members can visit other branches (its members may roam), and whether all its plans grant network access — or leave that off and set scope plan by plan under the plan's access rules (home only / all locations / custom list, with an optional tier ceiling).
-
Fine-tune pairs under WHO CAN VISIT WHERE — the access matrix. One row per home branch, one chip per host: switch a chip off and that host stops admitting that branch's members, even though both branches are otherwise open to the network. Flipping a chip queues the door-terminal updates at the host automatically. A chip that a branch-level switch already blocks says so when tapped instead of silently doing nothing.
-
Visitor hours appear under every branch that hosts. There are three rows — Men, Women and Everyone else / unspecified. Tap a row, switch on Limit when visitors may enter, pick From and Until (the branch's local time; leave both unset for all day) and the days, then Save. A row left as Follows home plan imposes nothing extra.
-
Under Visit fees, set the per-visit fee for every home → host pair (in the agreement currency). Pairs only appear for branches that roam and branches that host.
-
Open Accounts → Inter-branch settlement at month end: each pair shows visits, the capped amount in the agreement currency and the host's books amount; mark them paid as money moves.
-
For the traffic behind the money, open Reports → Cross-location visits — network visits and settlement in one report: who visited where, when, and what each pair's month adds up to.
What you should see
A denied visitor's tap shows Out of hours at the door and is logged as "this location does not admit visitors at this time" in the access log; inside the window the same tap opens the gate and the visit appears under the host's attendance with the member's home branch.
If something goes wrong
- A visitor is refused all day at one branch — their home plan's window and the host's rule don't overlap (see the note above). Either widen the visitor hours, or sell that member a plan whose hours fit.
- Visitor hours are set but the face terminal still lets visitors in early — the new schedules haven't been pushed yet: open the admin app on a device on that branch's network and run the terminal sync (Settings → Devices → Sync schedules), or wait for the next automatic push.
- No visitor-hours rows under a branch — that branch has Hosts visitors switched off; visitor hours only matter for hosts.
- A pair is missing under Visit fees — one side isn't set to roam or host yet.
Still stuck? Email hello@prismgym.com — include your gym name, the device, and a photo of what you see.