WeHealth app login/signup blocked by backend assignment requirement: feature request — self-service account access not supported via Esper
Android
The WeHealth app requires devices to be pre-assigned in the WeHealth backend before you can log in or sign up. This article explains what's happening and how to resolve it.
Before you begin
This is a limitation of the WeHealth application itself, not the Esper platform. WeHealth enforces server-side device assignment as a prerequisite for user login or account creation. Esper cannot bypass or modify third-party app authentication logic.
How to verify this is a WeHealth backend requirement
- In the Esper Console, navigate to Devices & Groups → [Device Name] → Apps.
- Confirm the WeHealth app is installed and active.
- Verify the app is not blocked by a Blueprint policy.
- Navigate to Devices & Groups → [Device Name] → Blueprint.
- Review the following settings to ensure they're not restricting account creation:
- App Permissions
- Network policies
- Kiosk mode
- Clipboard access
- Overlay permissions
- If none of these Esper policies are blocking the WeHealth app, the login issue is caused by WeHealth's backend requirement.
How to resolve this
- Contact your WeHealth account administrator or WeHealth support.
- Request one of the following:
- Bulk pre-assignment of all affected devices and users in the WeHealth backend, or
- Enablement of self-service sign-up in your WeHealth tenant
- Once WeHealth completes backend assignment or enables self-service sign-up, test login on a device to confirm it works.
If login still fails after WeHealth backend assignment
If employees can still not log in or sign up even after WeHealth has completed backend assignment, this may indicate an Esper-side issue. Before contacting support, collect the following information:
- Affected Device ID(s)
- WeHealth app version
- Esper Agent version
- Screenshot or screen recording of the failure
Then contact Esper Support with these details.
Still need help?
If you have questions about this issue or need further assistance, submit a support ticket.
Please sign in to leave a comment.
Comments
0 comments