I’d like to request an enhancement to the OTP approval workflow for agent installation.

Currently, when a user attempts to install the Atera agent and is prompted for an OTP (which happens often because we have several clients in foreign countries with spotty internet), an email with the OTP code is sent to all agents. However, the email does not include any information identifying which device or user triggered the request.

In onboarding scenarios (for example, setting up 25 new users), multiple OTP prompts can occur at once, resulting in several emails with different OTP codes and no way to know which code belongs to which user. This creates confusion and slows down the onboarding process.

It would be extremely helpful if the OTP email included one or more of the following:

Device hostname and/or username

Public IP address

Any other unique identifier that ties the OTP request to a specific device or user

This additional context would allow us to quickly match each OTP to the correct user and streamline large-scale deployments.

Thank you for considering this improvement!