498
Overview
Two-part authentication allows clients to confirm they’ve attended a private training session by approving or declining a check-in alert sent via push notification or SMS. When enabled, this feature helps validate that services were delivered and prevents session credit misuse.
It also helps managers ensure payroll reflects only verified sessions.
Prerequisites
- Session templates configured in Core
- Notifications (Push or SMS) enabled for your account
- Clients using the mobile app or have an SMS-enabled mobile number
- Two-part authentication is set to No by default; manual activation is required
Tip: This feature is ideal for private training, where accurate tracking and billing are essential.
Set up Two-Part Authentication on Session Templates
1. Log in to your Hapana Core account
Visit core.hapana.com and log in with your credentials.
2. Navigate to Schedule > Session Templates
Click on Schedule in the top navigation, then choose or create a session template.
3. Activate Two-Part Authentication
In the session template settings:
-
Click the pencil icon to edit.
-
Locate the 2 Part Authentication toggle.
-
Set it to Yes.
Tip: Add this toggle to all templates where session authentication is needed. It applies to every session created from the template.
How It Works for the Client
4. Client checks in to a session
Once a client checks in via any of these methods:
- Kiosk Check-in
- Contactless Check-in
- Barcode scan
- Core manual attendance marking
- Session Detail screen checkbox
...the system automatically sends an authentication alert via push or SMS.
Tip: If clients don’t see the alert, instruct them to open the app and swipe down to refresh their home screen.
5. Client receives and responds to the alert
The alert redirects clients to the app’s home screen where they must either:
- Tap Approve – confirms attendance and marks the session as attended.
- Tap Deny – marks the session as unattended.
Clients cannot dismiss the prompt without responding.
System Behavior Based on Response
- Approved: Session remains marked as attended. A green message shows: “Client has authenticated Check-in.”
- No response yet: Message shows as “Authentication is Pending.”
- Declined: Session status changes to unattended. A red message shows: “Client declined check-in authorization.”
Reports and Tracking
Navigate to Reports > Client Check-ins to view:
- A dedicated Authentication Status column, showing whether a session was approved, declined, or is pending.
Expected Outcome
Once enabled and configured, only sessions confirmed by the client will remain marked as attended. This supports accurate billing, clearer reporting, and a more trustworthy client-business relationship.
FAQs
Q: Can I resend the authentication request?
A: No, but clients can refresh their app screen to see the pending prompt if it was missed initially.
Q: What happens if a client does nothing?
A: The prompt remains active on their app’s home screen until a decision is made.
Q: Does this affect group classes?
A: This feature is best suited for private sessions and should be applied to templates where 1:1 authentication is necessary.
For further support, reach out to our support team via [email protected].
