AirWatch Workspace ONE Hub: The employee experience app explained
Employee technology works best when the secure choice is also the easiest choice. AirWatch Workspace ONE Hub is the employee-facing application within the wider AirWatch and VMware enterprise mobility management offering. It gives staff a consistent place to open approved apps, see assigned work and company information, and get support while IT retains control of access, policy and device compliance.
The name reflects the product’s evolution. AirWatch Hub was later presented as VMware Workspace ONE Hub, combining the familiar app catalogue with news, tasks, notifications and links to organisational resources. It is not simply a renamed device management console: the console is for administrators, while Hub is designed to reduce the friction employees encounter when they need company tools.
For Australian organisations, that distinction matters. A sales representative moving between central Sydney and a regional office, a nurse completing rounds in Brisbane, or a transport worker using a mobile connection between Melbourne depots may need one dependable route to work information. Hub can put the right tool, task and support channel into that mobile routine.
Real value appears when deployment, identity and communication are planned together. A free trial can expose whether employees actually use the app, whether existing systems integrate cleanly and whether IT can support it without creating another portal to manage. The product supplies the frame; operational design determines the experience.
What AirWatch Workspace ONE Hub actually does
Hub is designed primarily for iOS and Android devices, with managed distribution and sign-in policies connecting it to the organisation’s mobility and identity services. Depending on the configuration, employees can use it as a curated app launcher, receive targeted notifications, complete assigned tasks and find help. A built-in web view can also provide access to approved online tools without asking staff to hunt for separate links.
| Area | Workspace ONE Hub | Intune Company Portal | Device management console |
|---|---|---|---|
| Main audience | Employees | Employees | IT and mobility administrators |
| Core experience | Managed app access, tasks, news and support | Company apps, resources, help and notifications | Enrolment, policy, compliance, inventory and assignments |
| Administrative role | Configure the catalogue, content, identity and access links | Configure Microsoft apps, resources and Intune policies | Set device controls and monitor estate health |
| Typical fit | VMware or mixed-environment rollout | Microsoft-centred environment | Back-office management for either ecosystem |
These categories can overlap, but they should not be confused. Hub improves the employee touchpoint; it does not replace enrolment, compliance or remote support in the console. Likewise, an employee portal cannot create an identity source or conditional-access policy by itself. For an AirWatch-focused rollout, the key question is whether Hub is configured as the front end to existing identity, productivity and service systems rather than used as another disconnected app.
Security, identity and device management
Security begins with the connection between Hub, the device and the identity service. In a well-configured Workspace ONE environment, managed enrolment, single sign-on and conditional access can restrict applications to approved users and suitable devices. Administrators can require a passcode, encryption and current compliance before sensitive apps open, while access rules respond to sign-in risk and application sensitivity.
BYOD needs a deliberately different policy from company-owned phones. Hub should expose only approved apps and content, while the console applies controls appropriate to the enrolment method and role. Australian teams should be clear about monitoring, support duties, loss procedures and what happens when employment ends; employee trust is stronger when the app makes those boundaries visible.
The Privacy Act 1988 and Australian Privacy Principles set the baseline for many organisations handling personal information. Clear privacy notices, defined purposes, limited access and documented overseas disclosures matter when Hub exposes directory details, task content or app telemetry. The notifiable data breach framework also makes rapid assessment essential. Hub controls can reduce exposure, but they do not replace a privacy impact assessment or incident-response process.
The Australian workplace context
Australian workplaces are well suited to a mobile employee touchpoint because teams are spread across Sydney, Melbourne, Brisbane, Perth, Adelaide and regional centres. Hybrid schedules mean many people divide work between a desk, home and client sites. Mobile apps are part of the daily routine, and staff often expect short tasks, quick approvals and timely notifications to work through a phone rather than wait for a laptop session.
The local market is not limited to large banks or government departments. Mid-sized professional services firms, logistics operators, retailers, manufacturers and healthcare providers also support mobile workers, often with a mixture of corporate devices and personally owned phones. In regulated sectors, app security may need to align with sector obligations as well as general privacy and cyber guidance; healthcare, education and critical-infrastructure environments can require tighter access rules than a standard BYOD programme.
Field realities deserve equal attention. A worker using a phone at a construction site or roadside depot may have intermittent connectivity and may need Hub content available without exposing sensitive cached data. Safe Work Australia and state work health and safety laws also mean communication and task workflows should support safe work, not create pressure to respond while a person is in immediate danger. Offline behaviour, escalation and emergency procedures therefore belong in the pilot brief.
A practical rollout checklist for Australian teams
A strong deployment starts with a narrow employee journey. Define one or two jobs for Hub, identify the apps and content required, and name the owners who will maintain them. The experience should feel faster than the existing mix of links, native apps, email requests and phone calls; otherwise, it becomes another place employees must check. Use the following actions to make that experience practical and governable.
- Map a priority employee journey, then remove duplicate applications, links and manual approval steps that Hub can replace.
- Segment access by role, device ownership and risk so that BYOD users receive an appropriately different experience from corporate-device users.
- Connect Hub to identity, catalogue, service desk and task systems, then test single sign-on and conditional-access behaviour.
- Pilot with a representative cohort drawn from office, frontline and regional teams rather than limiting feedback to enthusiastic volunteers.
- Publish clear guidance covering privacy, acceptable use, support channels, lost devices and the offboarding process.
- Test weak coverage, app updates, revoked access, device loss and employee departure before expanding beyond the pilot.
- Measure adoption and service outcomes, while assigning ownership for content updates, integrations, policy reviews and user support.
Run the pilot long enough to observe real work cycles. Installation figures are useful, but task completion, support requests and employee feedback provide a better basis for decisions. Review results with security, HR, internal communications and the service desk, then correct confusing workflows before adding more content. A smaller Hub that people trust can deliver more value than a comprehensive catalogue that feels like another compulsory app.
Measuring value and starting a focused evaluation
Measure outcomes rather than download counts. Useful indicators include the time required to install or find an app, completion of assigned tasks, adoption of single sign-on, onboarding time, help-desk demand and the rate of users who can access only what their role requires. Establish a baseline before launch and compare the pilot with the previous process, including the work required from service-desk staff.
Package fit matters as much as feature count. Hub can sit within a broader Workspace ONE edition, while device management, identity, endpoint security and advanced access may depend on the selected package and existing investments. Review current pricing and package comparisons, then use relevant customer stories to test assumptions about scale, support and adoption. A trial should include representative integrations, not a simplified demonstration.
AirWatch offers a fully functional 30-day free trial, giving an Australian team room to test Hub with real workflows, realistic security settings and a representative group of users. Review the available packages, evaluate implementation effort and contact sales to discuss licensing or integration requirements. Start the trial, select a clearly defined pilot cohort and build the rollout around measured employee and administrator needs.