The Device authentication feature in pixi strengthens security by introducing device trust policies for pixi Mobile (.NET MAUI) and pixi Connector. While Multi-Factor Authentication (MFA) is already supported for the login go pixi web, traditional MFA methods (like email or app-based verification) are often unusable in warehouse environments where workers may not have business email accounts or access to personal devices. The device authentication addresses this gap by allowing administrators to manage and enforce trusted device policies as an alternative form of identity assurance.
This guide is intended for administrators.
User Permissions
Administrators can access the Devices page by default. Users will have to have the permissions assigned under their role. To enable the permissions:
Navigate to Administration> User Administration > Roles > General Permissions.
Edit the section and enable Devices.
Click Save.
The role now has access to the Devices page and all can perform all related actions.
Devices List Overview
The devices page features the following information:
Type: Indicates the device category, either Mobile or Connector.
Name: The user-defined or system-assigned name of the device.
Description: Optional text providing additional context or details about the device.
-
Status: Reflects the trust level of the device:
Pending: Device has been registered but not yet reviewed.
Trusted: Device was approved and permitted.
Untrusted: Device is denied access.
Device ID: A unique identifier assigned to each device; practical when multiple people share the same device or device names are identical because they have the same manufacturer name in the Name column (for example, "Zebra TC22") . Also identifiable in pixi Mobile Settings under Device Id.
Created: Timestamp showing when the device was added.
Created By: The user who registered the device.
Modified: Timestamp of the last update to the device record.
Modified By: The user or process that last modified the entry.
How to Mark A Device as Trusted
Follow these steps to authenticate devices:
Log in to pixi Web and navigate to Administration > User Management > Devices.
Enable the checkbox of the device you'd like to mark trusted. Note that you can select multiple entries.
Click Mark Devices as Trusted via the checkmark in the navigation bar.
In the popup, confirm your choice.
The device is now marked as trusted and can login.
Tip: To view all pending requests for devices, drag and drop the Status column into the column sorter below the navigation bar.
How to Mark a Device as Not Trusted
Follow these steps to revoke access to pixi for a device:
Log in to pixi Web and navigate to Administration > User Management > Devices.
Enable the checkbox of the device you'd like to mark trusted. Note that you can select multiple entries.
Click Mark Devices as Untrusted via the prohibited symbol in the navigation bar.
In the popup, confirm your choice.
The device is now marked as not trusted and cannot login anymore.
If you would like to mark the device as trusted again, follow the steps on How to Mark A Device as Trusted.
Deleting a Device
Proceed as follows to delete a device from the device list:
Log in to pixi Web and navigate to Administration > User Administration > Devices.
Select the checkbox for the device you want to delete. You can select multiple entries.
Click Delete in the navigation bar.
In the popup, confirm your choice.
Questions about Device Authentication
What happens if a Device ID is deleted from the database?
If a Device ID is deleted from the database (removing the associated secret key and preventing mobile login), the device registration process restarts. The user will need to log in as if for the first time. The device is re-registered using the same secret key, and an administrator must confirm the registration before the user can access the system.
Why do I need to re-trust my device after reinstalling the pixi Mobile app?
If you uninstall and then manually reinstall the pixi Mobile APK, the app generates a new Device ID. Because this Device ID is treated as a new device, the corresponding record must be marked as trusted again before the device can be used normally.