Mobile check-in and devices
Your team can check in and out from the Webelio phone app. To keep those punches honest — the right person, at the right place, from one phone — you control a few settings on the Attendance Permission screen.
These controls only affect mobile punches. Punches from a web browser or a biometric machine are never location-checked.
Turning mobile check-in on
Mobile check-in works once the app is installed and the person has a portal login. What you decide here is how much proof each punch must carry.
Location capture
You can require a punch to record where the phone is. Choose the capture mode for your organisation:
| Mode | The phone records location on... |
|---|---|
| Off | Never — no location asked |
| On check-in | Only when clocking in |
| On check-out | Only when clocking out |
| Both | Clocking in and out |
When a mode requires location and the phone can't provide it, the punch is refused (see failures below).
Geofencing
Turn on the geofencing master switch to go a step further: a punch must not just record a location, it must be inside the allowed area around the branch. This is the switch (also under Settings → Attendance) that enforces "you can only punch at work".
To use it, give each branch a location. In Settings → Locations, set the branch's latitude, longitude, and radius (there's a "use my current location" helper and a map preview). The radius is how far from that point counts as "at work".
If a branch has geofencing on but no location set, Webelio lets the punch through rather than locking people out of a misconfigured branch. The Attendance Permission screen flags any branch in that state so you can finish setting it up.
Per-employee overrides
By default every person inherits your organisation settings. On the Attendance Permission screen you can override an individual — for example, turn location off for a field sales rep who is never at a branch. Leave an override blank and the person follows the organisation default. You can also select several people and change them together.
One phone per person
Each account is tied to one mobile device. The first phone someone signs in from becomes their bound device. If they try to sign in from a different phone, they're blocked until you reset them — this stops one person punching for another.
When someone genuinely changes phones (new device, lost handset), use Reset Mobile Login on their row. That unbinds the old phone (it signs out) and lets the next phone they sign in from become the new bound device. Their web and portal sessions are untouched.
Punch failures and what to do
When a punch is refused, the worker sees a clear reason. Here's what each means and your fix:
| The worker sees | What happened | What you do |
|---|---|---|
| Location required | Capture is on but the phone didn't share a location | Ask them to allow location for the app, then punch again |
| Outside the allowed area | Geofencing is on and they're too far from the branch | Confirm they're at the right branch; widen the branch radius or fix its coordinates in Locations if it's set too tight |
| Device not registered | They're on a different phone from their bound one | Use Reset Mobile Login so their new phone can bind |
What's next
- Set branch locations — coordinates and radius for geofencing
- Attendance settings — the org-wide switches
- Check-in for employees — what your staff see