Device linking: The best solution to prevent attendance fraud

The process of recording attendance through the Jisr mobile application or tablets has become the prevailing standard. However, with this advancement, challenges have emerged regarding ensuring the accuracy and reliability of attendance data, chief among them being the phenomenon of "proxy attendance" (known as "Buddy Punching"), where one employee records attendance on behalf of a colleague.

To address this challenge, a crucial feature known as the "Device Linking Policy" was developed.

Note: If you wish to activate the feature, please contact your customer success manager or the support team at Jisr.

What is the Device Linking Policy?

The Device Linking Policy is an administrative security system aimed at restricting employee access to the attendance system (or sensitive work applications) to be confined to one approved device per employee.

Once this policy is activated, the device the employee first logs in with becomes the "activated device" linked to their account. Any attempt to log in from another unlinked device, or an attempt by a colleague to log in using that device, will be blocked.

Note: The mobile phone already used by the user, even before the feature is activated, will be the same activated device associated with the employee.

Key Operating Mechanisms of the Policy

• Auto-Linking: Upon the employee's first login to the app after the policy is enabled, their device is automatically and exclusively linked to their account.

• Preventing Sharing: If any other employee attempts to use the same device, their request will be immediately rejected with the message: "This device is linked to another account."
  

• Device Change Requires Approval: If an employee wishes to use a new device, they must submit a linking request, which is sent to their manager for approval, ensuring full control over the process.

Steps to set up an Approval workflow for device connection requests:

1. From the "Settings" screen

2. Select "Requests"

3. Go to the "Device link" request to set up the approval workflow for when an employee requests to connect a device.

Practical Example of Implementing the Device Linking Policy

Let's assume "Company X" has implemented the Device Linking Policy for all its employees to prevent attendance fraud via the Jisr application.

Case One: Preventing Proxy Attendance

Employees:

• Khalid: An employee linked to his private device (Khalid's Device).

• Mansour: Khalid's colleague, who is also subject to the policy.

Step	Action	System Result	Achieved Goal
1. Auto-Linking:	Khalid logs in for the first time using his device.	Khalid's Device is automatically linked to Khalid's account.	Ensuring one trusted device for Khalid.
2. Attempted Fraud:	Khalid forgot his device. Mansour tries to log in using Mansour's account via Khalid's Device (which is linked to Khalid).	Mansour is blocked, and the message "This device is linked to another account" appears.	Preventing Mansour from using Khalid's device and maintaining link integrity.

Case Two: Requesting a New Device Link

Employees:

• Mariam: An employee linked to her old device (Device 1).

• Fatimah: The Manager responsible for approval.

Step	Action	System Result	Achieved Goal
1. Device Change:	Mariam purchases a new phone (Device 2) and attempts to log in to the Jisr app with it.	The login attempt is rejected because Device 2 is not linked to Mariam's account.	Enforcing adherence to the registered device.
2. Submission of Request:	Mariam must submit a request to link Device 2 via the application.	The request is automatically sent to Fatimah (the approved manager).	Ensuring administrative review and approval before linking a new device.
3. Approval:	Fatimah approves the request.	Device 2 is linked to Mariam's account, and Device 1 may be unlinked (depending on system settings).	Allowing Mariam to use the new device after formal approval.