Mobile Device Management
Manages the device itself: enrollment, OS-level policies, encryption requirements, remote lock and full-device wipe. The foundation every fleet starts with.
BlueMail deploys, configures and governs itself through the device management platform you already run. Push a policy once and it lands on every device, while personal data stays personal.
The industry loves its acronyms. Here's what each one actually means, and where BlueMail fits. Spoiler: it works with all of them.
Manages the device itself: enrollment, OS-level policies, encryption requirements, remote lock and full-device wipe. The foundation every fleet starts with.
MDM plus the app layer: app distribution, managed configurations, per-app policies and content controls. This is where BlueMail plugs in deepest.
One console for every endpoint: mobile, desktop, rugged. BlueMail runs on iOS, Android, Windows, Mac and Linux, so a single UEM policy covers your whole fleet.
Controls the app, not the device. Ideal for BYOD: wipe BlueMail's corporate data without enrolling, or ever touching, an employee's personal phone.
No proprietary agent, no parallel console. BlueMail speaks the AppConfig Community standard, so it behaves like a first-class citizen in every major management platform.
Managed app config, app protection policies and conditional launch, with Microsoft Entra ID signals built in.
Managed distribution and configuration for Apple fleets, Mac and iOS side by side.
AppConnect containers and standards-based managed configurations for regulated industries.
Rugged, kiosk and single-purpose deployments with locked-down profiles.
BlueMail follows the AppConfig Community standard, so any standards-based platform works out of the box.
Define the configuration once in your MDM and BlueMail reads it on first launch: account, servers, authentication, security posture. Variables like the user's principal name resolve per device, so one payload provisions a thousand inboxes.
Policies are enforced at the app level and re-evaluated continuously. Change a rule in your console and the fleet follows. No reinstall, no re-enrollment.
Most of your workforce reads corporate email on a personal phone, and they shouldn't have to hand it over to IT to do so. BlueMail supports app-level management (Android Enterprise work profiles, Apple User Enrollment and pure MAM deployments), so your policies govern the corporate inbox and nothing else.
IT can enforce lock-screen rules, block risky attachments and wipe corporate mail the moment someone leaves. What IT can never do is see personal photos, private messages or browsing history. That line is architectural, not a promise.
Zero-touch deployment through your MDM. BlueMail lands on every managed device silently. No user setup, no IT tickets.
Push accounts, servers and branding as a managed configuration. Employees open the app and their corporate inbox is simply there.
App-level policies follow the device everywhere: lock-screen rules, copy-paste boundaries, attachment handling, screenshot control.
Offboarding is one action: revoke access and wipe corporate data remotely, while personal photos and chats stay untouched.
Lost device? Remotely lock or wipe BlueMail data without touching the rest of the phone.
Gate inbox access on device posture, network conditions and authentication strength.
Fleet status, compliance posture and policy pushes, one pane of glass for IT.
Any platform that implements the AppConfig Community standard, including Microsoft Intune, Jamf Pro, Ivanti (MobileIron) and SOTI MobiControl. If your EMM can push a managed configuration, it can manage BlueMail.
No. BlueMail works inside Android Enterprise work profiles, Apple User Enrollment and pure MAM deployments, so IT governs the corporate inbox without enrolling, or even seeing, the rest of the device.
One action in your console revokes access and wipes BlueMail's corporate data remotely. Personal photos, messages and apps are untouched. The wipe scope is the app, not the phone.
Yes. Push account, server and policy settings as a managed configuration; variables like the user principal name resolve per device, so a single payload provisions the entire fleet.
They're complementary. Your MDM handles deployment and device-side policy; the Admin Console adds BlueMail-side fleet visibility, usage insights and email-specific controls.