Attention: Check our plans by clicking here!
This article presents the basic concepts of the User Management and Authentication functionality of Pulsus MDM. Here, you will understand the purpose of this tool, who benefits from it, what the technical requirements are, and the difference between the user profiles available in the system.
System Prerequisites
Before enabling the functionality for your fleet, ensure that your devices and the system meet the mandatory specifications below:
Operating System: Android 6.0 or higher.
Management: Fully Managed or Device Admin (deprecated)
Pulsus Agent Version: The Pulsus application installed on mobile devices must be version 7.2.00 or higher. If your devices are outdated, perform the application update process directly through the administrative panel before activating authentication.
What is it and what is it for?
The User Management functionality changes the paradigm of corporate mobility. Instead of management focused purely on the physical device (Device-Centric), Pulsus begins to work with an identity-centric approach. This establishes a direct, secure, and traceable connection between the employee and the company's device.
It was developed to meet two complementary needs:
For the IT Administrator (Focus on Governance): Allows mapping and nominally identifying who is operating each device in the field. It eliminates the classic problem of "informal transfer" (when employees swap cell phones among themselves without notice), reduces asset loss, ensures corporate data protection, and generates precise reports for legal and security audits.
For the Employee: Guarantees a fluid, personalized, and secure work environment. The professional gains the ease of quickly authenticating, having a clean digital environment, and acting in compliance with the company's privacy guidelines.
User Profiles: Authenticated vs. Inventory
To intelligently organize and control your operation, Pulsus allows employees to be registered on the platform under two distinct profiles:
1. Authenticated User
Definition: This is the employee registered with active access credentials (username and password).
Behavior: When turning on the cell phone or tablet, the employee sees an authentication screen and must enter their access data to release the use of corporate applications (on devices that have the authentication policy enabled).
Recommended Use: For all operations that require nominal access control, daily log traceability, and physical security lockdown.
2. Inventory User
Definition: This is the employee registered without a password definition (with the password option deactivated in the administrative panel).
Behavior: This user cannot log in to the mobile device. Their function is strictly administrative: to serve as an identification tag in the Pulsus panel for IT to manually link the employee to the respective device under their physical responsibility.
Recommended Use: Perfect for internal stock control, cost center monitoring, and equipment distribution without the need to enforce password login on the device. It also functions as an initial step for companies that want to organize their base before requiring authentication lockdown at the endpoint.