What are the unique identifiers for recipients and desktops?

Manually Added Individual Recipients: Unique identification is based on matching the recipient’s email, followed by text number if available. The Unique ID field is not used as an identifier for manually added recipients.
Bulk Upload Recipients: Unique identification is matched first by email, then by text number, and lastly by the Unique ID field if needed.
sFTP Imported Recipients: Unique identification relies on a 'Unique ID' data field, which is mandatory for sFTP imports.
Azure AD Synced Recipients: Unique identification relies on a 'Unique ID' data field, which is mandatory for Azure AD sync. The unique identifier options for Azure are 'UserPrincipalName', 'UserID', or 'EmployeeID'.
Recipient API Synced Recipients: The Recipient API does not require a unique identifier for recipients. Any recipient data passed through the Recipient API will be added without a Unique ID requirement. RedFlag doesn’t check for uniqueness if it is provided through the recipient API. RedFlag will update the recipient profile with the data as provided through the recipient API.

The unique identifier for desktops is the Device Name. This Device Name is automatically captured when the Desktop App is installed and activated on the desktop. For desktops individually added or added/updated via bulk upload in the platform, the Device Name is required for the database entry and for profile updates used in grouping.