In addition to deeper integration, it would be extremely valuable if Hudu could automatically associate devices with users based on available data — either through N-Central, Entra ID, or Active Directory information.
The goal is to have an immediate and accurate view of which user is currently using a device, and optionally, who has used it previously.
For example:
• When a device syncs from N-Central, Hudu could match it to a user based on the last logged-in username, AD account, or Entra ID.• If the identifier is unclear, rule-based logic (e.g., by email or asset tag pattern) could be applied.• The matched user would automatically appear on the device card for instant visibility during support cases.• A historical record could track previous user assignments for auditing or troubleshooting.This feature would make Hudu a much more powerful support and operations tool, allowing technicians to instantly identify the right endpoint for a user, improve response time, and ensure more accurate lifecycle and licensing management.
In short, we’re requesting a built-in device-to-user mapping automation feature — with optional historical tracking — to bridge the gap between asset data and user context in real time.