AirWatch role-based access control: assigning admin permissions
AirWatch role-based access control is the mechanism that turns administrator jobs into governed entitlements. Instead of giving every support specialist the same elevated permissions, an organisation can assign roles containing only the device, application, identity and reporting actions that person needs. This approach, commonly called RBAC, limits the impact of mistakes, compromised credentials and overly generous access while preserving the speed employees expect from IT support.
For Australian enterprises, the value is especially practical because staff commonly move between offices, homes and client sites while using company phones, personal devices and cloud applications. A role structure lets a central service desk support a user working from Melbourne while keeping device-group boundaries intact for fleets in Brisbane. It supports BYOD and remote work without treating every endpoint as equally sensitive.
Why broad administrator access creates avoidable risk
Administrator access is often designed as a simple choice between no access and full access. That creates two problems: routine support staff either receive too much privilege, or receive too little and route every task to a small platform team. The second becomes a bottleneck when a Sydney office opens before an overnight administrator in another time zone begins work; the first increases the number of people able to change enrolment, compliance and data-access settings.
Named administrator accounts also produce cleaner evidence than shared logins. When a change must be investigated, audit records should identify the individual who approved, configured or revoked access, not merely a generic service-desk login. RBAC supports separation of duties by separating policy administration, device support and oversight. It also makes onboarding, temporary leave and offboarding easier because access can be attached to a role and adjusted without rebuilding every permission individually.
Model roles around actual responsibilities
Begin with the duties in the role description, not with the permissions exposed in a menu. Translate broad labels such as “mobile administrator” into concrete tasks: enrolling devices, assigning applications, adjusting compliance, supporting users, reviewing logs and administering access. Each task should map to a named role so that an auditor can trace it to an operating procedure.
Build a small role family rather than dozens of one-off profiles. A platform super administrator can own global configuration and role management, while an IT administrator manages policy and devices for assigned groups. A help desk role can handle enrolment and resets, and a read-only oversight role can examine evidence without changing it. The names are organisational conventions; map them to the roles and actions available in your AirWatch tenant.
Where a tenant supports role hierarchy, AirWatch RBAC can build lower roles from an approved parent role and grant only the additional actions each team needs. Inheritance reduces duplication, but it can also conceal effective permissions if nobody checks the combined result. Document direct grants, inherited access, scope and approval owner. If a temporary contractor needs elevated access, assign a time-limited role and make expiry automatic rather than relying on a manual reminder.
Assign permissions and define their scope
In common AirWatch and Workspace ONE console layouts, navigate to Users & Groups, locate the named administrator, open Edit, and use the Roles tab or role-assignment panel. Add the required role, choose a device-group scope, save, and verify that inherited permissions match the job. Menu labels and available actions can vary by licensed console version, so validate the procedure in a test tenant rather than relying on a generic click path.
AirWatch, now within VMware’s endpoint-management portfolio, may sit beside other management tools in the Australian enterprise market. Where the estate includes Windows devices, a Windows endpoint management comparison can help teams confirm which platform should own enrolment, policy and application deployment. The aim is to avoid duplicating administration and instead make ownership explicit, especially for devices that move between office and home networks.
Use individual named identities for every privileged assignment. Shared administrator logins defeat attribution and complicate revocation when a team member changes roles. For users who need several responsibilities, attach the relevant roles to their identity or to a carefully managed group. Give groups only stable membership rules and review group owners, since an unexpected addition can silently expand access for every member.
Test administrator access and review it regularly
Pilot each role with a test identity and a short list of required and forbidden actions. Confirm that the person can enrol a device, deploy an application, read a compliance record or change policy as intended, and that they cannot perform neighbouring actions outside scope. Compare observed behaviour with the role definition after every change, not only when the account is first created.
Build support tiers around operational risk. Frontline staff may need enrolment, password resets and basic troubleshooting, while policy exceptions and identity administration should remain with a smaller specialist group. Where network changes affect device connectivity, specialist identity and network expertise from JMA Wireless advisers can help separate access decisions from infrastructure troubleshooting without granting both sets of permissions to one account.
Review effective access on a defined cadence and whenever responsibilities change. Export or review role assignments, group membership and recent administrative activity, then remove dormant privileges and orphaned accounts. Include contractors and staff returning from extended leave. Recording the business owner, approval date and expiry for elevated access creates evidence that the permission model remains accountable over time.
Align access with Australian privacy and security duties
The Privacy Act 1988 (Cth) and Australian Privacy Principles govern many organisations that handle personal information, including employee records and BYOD data. APP 11.2 requires reasonable steps to protect information, so administrator roles should limit who can view user identifiers, device ownership, location data, diagnostics and application content. State and territory privacy or health-information laws may also apply, depending on the organisation and data, so the role design should fit the legal obligations applying to each business unit rather than assume one national rule covers every record.
Access governance also supports the Notifiable Data Breaches scheme administered by the Office of the Australian Information Commissioner. If an unauthorised administrator exposes personal information, clear role boundaries, MFA and reliable audit trails help contain the incident and establish what happened. The Australian Signals Directorate’s Essential Eight provides another useful control reference for MFA, patching, logging and access restrictions; it is not a blanket legal mandate for every business, but alignment supports procurement, assurance and incident readiness.
This matters across the local market, where service desks may support staff in healthcare, education, government and professional services with different risk tiers. Give a public-sector laptop or a clinical device a more restricted role than a low-risk test handset, and keep remote wipe and data separation permissions separate from routine support. MFA for privileged access should be the default, with exceptions documented and time-limited.
Compare common role profiles and start a controlled rollout
Before assigning a role, define its business owner, the people it covers, its permitted actions, its device and organisation scope, and the approval needed to change it. A concise role standard prevents an administrator from interpreting a vague label as permission to do anything. It also gives auditors a consistent basis for comparing access across teams.
The following profiles are a practical starting point for design, not fixed product labels. Map each one to the role structure supported by your licence and tenant, then remove actions that are unnecessary. That adjustment prevents a convenient help-desk function from becoming an unintended administrative backdoor.
| Role profile | Primary duties | Recommended scope | Permission boundary |
|---|---|---|---|
| Super administrator | Platform configuration, role management and emergency administration | Entire platform for a very small named group | MFA, credential vaulting, peer approval and monitored break-glass use |
| IT administrator | Device policies, applications, compliance actions and user support | Named device groups and assigned user groups | Cannot approve or administer its own role |
| Help desk | Enrolment, device reset, basic troubleshooting and user guidance | Enrolment and support groups | No policy changes, role management or unrestricted data visibility |
| Read-only auditor | Review configuration, activity logs and compliance evidence | Relevant organisational or device-group scope | No create, edit or delete actions |
Start a controlled rollout with a 30-day fully functional free trial, using representative devices and test identities to validate each role. Compare the available packages and pricing, read customer stories about similar deployments, and bring your proposed role matrix to the sales team. A successful first phase ends with documented assignments, approved scopes and evidence that support teams can work quickly without carrying unnecessary privilege.