Separate organization truth from location context
Keep a single organization-wide member identity while attaching attendance, staff responsibility, and kiosk activity to the location where the work occurs.
Define whether a member has one home location, can attend any location, or requires approval to move. Make that rule visible to staff before it becomes an exception at the desk.
Assign permissions around real responsibility
Organization owners and administrators need cross-location oversight. Location managers need enough authority to run their site. Staff should see and change only what their daily work requires.
Write permissions as actions: invite staff, edit a member, resolve a blocked visit, manage a kiosk, export records, or change organization settings. Avoid vague labels such as ‘full access’.
- Every role has a named operational owner.
- Location-scoped roles cannot act in another location.
- Billing is visible only to organization owners and administrators.
- Privilege changes are reviewed and leave an audit event.
Treat every kiosk as a scoped device
Pair each kiosk to one organization and one location. Give it a revocable device credential rather than a staff member’s account, and define who can approve or revoke it.
Set an idle-reset expectation that matches the physical environment. The next visitor must never inherit the previous visitor’s confirmation or search state.
Watch for thisA kiosk is not a small admin dashboard. Keep navigation, personal information, and recovery controls intentionally limited.
Create one escalation path
Document which issues stay local and which move to an organization administrator: unknown member, wrong home location, suspended status, staff access, device revocation, and data correction.
Use one shared language for states and resolutions across locations. This makes reports comparable and prevents each site from inventing a different workaround.
Review the network, not only each site
Compare attendance volume, unresolved exceptions, duplicate attempts, and inactive-member patterns by location. Look for process differences before assuming one team is underperforming.
A regular cross-location review should end with an owner and next action for each material exception. Reporting is useful only when it changes the operation.