Restricting mobile check-in to a registered phone

Restricting mobile check-in to a registered phone

Registered phone only ties each employee's mobile check-ins to one phone, so nobody can log in on a colleague's phone and check in for them. Use this to stop buddy punching, to reset an employee's phone when they get a new one, or to let someone check in from a shared company phone. With the rule on, mobile check-in, check-out and breaks only work from the phone each employee is registered to.

Where:

  • The company rule: Attendance › Settings › Attendance Rules, or Settings › Calendar › Attendance Rules, in the Check-in & check-out section
  • One employee: their profile › Attendance › Check-in Settings › Identity verification

You need:

  • The Attendance Settings right to change the company rule
  • Access to edit the employee's attendance settings to reset a phone

How a phone becomes the registered phone

You do not register phones yourself. The first phone an employee logs in on, or opens the KAMI app on while logged in, becomes their registered phone. KAMI never replaces it afterwards, unless the phone is reset.

This happens whether the rule is on or off. So most employees who use the app already have a registered phone before you turn the rule on, and it may be an old or borrowed one. Check the Registered phone line on a few profiles first.

An employee with no registered phone yet can check in from any phone. Their next login or app start registers the phone they use.

How to turn the rule on

  1. Go to Attendance › Settings › Attendance Rules.
  2. In the Check-in & check-out section, select Edit.
  3. Turn on Registered phone only, then select Save.

The Check-in & check-out section of Attendance Rules, showing the Registered phone only setting switched Off

The rule is Off by default and applies to everyone in the company as soon as you save. Tell your employees first.

If you turn the rule off, employees can check in on any phone. Their registered phone stays on their profile, so when you turn the rule back on, KAMI uses it again.

How to check or reset an employee's phone

  1. Open the employee's profile and select Attendance.
  2. Scroll to Check-in Settings, then Identity verification.
  3. Read the Registered phone line. It shows Registered on followed by the date, or No phone registered yet. It does not show the phone itself.
  4. To change it, select Edit on the Check-in Settings card, then select Reset Phone and confirm.

The Identity verification group on an employee's Attendance page, showing Any phone check-in, the Registered phone line and the Reset Phone button

After a reset, the next phone the employee logs in on or opens the app on becomes their registered phone. Ask them to do that on the phone they want to keep.

Note: On an iPhone, the registration survives reinstalling the app. On Android, a reinstall wipes the phone ID, so the employee needs a Reset Phone before they can check in again.

How to let someone use a shared phone

  1. Open the employee's profile and select Attendance.
  2. Select Edit on the Check-in Settings card.
  3. Under Identity verification, turn on Any phone check-in, then save.

That employee can then check in from any phone, while everyone else stays restricted.

What employees see

Employees can still log in on any phone, request leave and view payslips. Only mobile check-in, check-out and breaks are limited. Offline check-ins uploaded from another phone are refused too.

If an employee tries to check in from a phone that is not their registered one, they see:

You can only check in from your registered phone. Ask HR to reset it if you changed phones.

If the app does not send a phone ID, for example because it needs an update, they see:

Update the app to check in from this phone.

Tablets and web check-in are not affected by this rule.

Following up on refused check-ins

Refused check-ins appear in Mobile Check-in Errors, under Attendance › Tools & Reports, where the report shows each failure with its reason. Check it after you switch the rule on to see who needs a reset or an app update.

Resetting a phone and changing Any phone check-in are recorded in the employee's audit trail under Attendance.

What Happens Next

Once the rule is on, every refusal is a mobile check-in, check-out or break from a phone other than the employee's registered one. Nothing changes for tablets, web check-in, leave requests or payslips. The employee is not locked out of the app, so a refusal is a prompt to use their own phone or to ask HR for a reset.

Tips

  • Announce it first. The rule takes effect for everyone the moment you save it, and anyone using a phone other than their registered one is refused straight away.
  • Ask employees who changed phones to tell you before go-live. Resetting them in one pass avoids a queue of refusals on the first morning.
  • Turn on Any phone check-in before go-live for shared phones. Otherwise those employees are refused on every phone but their registered one.
  • Check Mobile Check-in Errors in the first week. It shows who was refused and why.
  • Keep resets with HR. Because a reset lets the next phone register, a free-for-all reset would let someone check in for a colleague and switch back.

Troubleshooting / FAQ

An employee says they were refused on their own phone. Their registered phone is an earlier one. Use Reset Phone, then ask them to log in on the phone they want to use.

An employee got a new phone and cannot check in. Use Reset Phone. Their next login on the new phone registers it.

An employee can log in on a second phone but cannot check in or out. That is expected. They need to use their registered phone, or HR can reset it.

Anyone can check in from any phone. Check that Registered phone only is turned on in Attendance Rules.

An employee on a shared phone is refused. Turn on Any phone check-in for that employee in Identity verification.

An employee sees the message asking them to update the app. Ask them to update the KAMI mobile app and log in again.

Can employees reset their own phone? No. Someone with access to their attendance settings has to do it.

Related articles