Device Binding – Feature Guide

1. Feature Overview

Device Binding is a mobile security feature that ensures users access the LeadSquared mobile app only from a single, registered device. This protects sensitive business data, maintains accurate location tracking of the user, and prevents unauthorized access. Device Binding ties a user’s mobile app login to one specific mobile device. Once a device is bound:

• Any login attempt from a different device is automatically blocked.
• Only an admin can approve or reset the device binding to allow access from a new device.

2. Prerequisites

• Device Binding is a feature only for LeadSquared Mobile App users.
• This feature is available only if you have enabled Location Insights in your account. To enable Location Insights and Device Binding, reach out to support@leadsquared.com.

3. How It Works

• Once enabled, Device Binding automatically links a user’s account to the first mobile device they log in with.
• If a user upgrades or changes their device, they must send a device binding request to their admin to register the new device.
• From the LeadSquared Web App, admins can manage device registrations by:
  • Approving or rejecting new device requests
  • Unmapping existing devices when required

4. Device Binding on LeadSquared Mobile App

Once Device Binding is enabled, the mobile user will be logged in seamlessly. This device will become their bound device for all future logins. If a user needs to switch to a different device, there are methods to do so. These options are described in the sections below.

4.1 Login using Unregistered Device

If a user logs in on a new, unregistered device, a non-dismissible pop-up appears saying “This device is not registered with us. Please contact your admin to register this device.”

From here, the user can make one of these choices:

• Contact Admin – Sends device binding request to admin, displays “Request Sent”, and logs the user out.
• Cancel – Logs the user out without sending a request.

4.2 Login using Unmapped Device

In certain cases, the admin can unmap a user’s device (for example, if the device is lost or stolen). If a user tries to log in from a previously registered device that has been unmapped, they will see a pop-up message: “This device is no longer linked to your account. Please contact your admin to regain access.” They will be logged out immediately. The user can then attempt logging in again, which will trigger the Login Using Unregistered Device flow.

5. Device Binding Management on LeadSquared Web App

Admins get full access to all details about the users’ registered devices from the Device Binding page on the LeadSquared Web App.

5.1 View Bound Devices

To view the bound devices of all users –

1. Navigate to Apps>Field Sales Territories>Device Binding.
2. All the registered devices and their details are displayed under the All User Devices tab.

Alternatively,

1. Navigate to Apps>Location Insights>Device Binding.

5.2 View Device History

To view a user’s device history, click the icon next to their name. This will display a list of all devices the user has previously registered with LeadSquared along with its platform, model, OS version, app version and other device-related details.

5.3 Approve / Reject Devices

Admins can approve or delete device binding requests sent by mobile users from Location Insights>Device Binding>Approval Requests tab in web app. The admins can:

• Approve – Marks new device as approved, unmaps old device, sends notification that says, “New device registration request approved”.
• Delete – Discards the request, shows toast “Request Deleted”.

Once the new device is approved, the user can log in and continue with their daily workflows.

5.4 Unmap User Devices

If a user loses their device or no longer has access to it, they can request the admin to unmap it. Once unmapped, the lost or stolen device will no longer provide access to any data. Admins can complete this action directly from the web app by unmapping the user’s active device.

Any Questions?

We’d love to answer your questions or hear your own unique use cases. Feel free to share your experiences in the comments section below.