Role-Based Access

Simply set individual permissions for specific users and groups to dramatically reduce your attack surface.

What is role-based access control?

Role-based access control or RBAC is an approach to restricting system access to authorized users. RBAC is a policy-neutral access-control mechanism defined around roles and privileges. RBAC can be used to facilitate the administration of security in large organizations with many users and permissions.

Role-Based Access Control (RBAC) functionality allows you to assign owners and lock down access where appropriate. If you are managing many unique organizations or subsidiaries internally or for your customers, modern management tools can allow you to easily move between different instances.

Patching and cyber hygiene solutions can be very powerful tools. Automox’s RBAC controls ensure that users are only able to access the features required for their role, improving operational security within your IT organization.

RBAC goes global

Improve your cyber hygiene by specifying who has access to which systems and tools.

Learn more

Automox data sheet

Key benefits and technical requirements of our cloud-native patch management tool.

Learn more

Control access by role

Full admin

A Full Admin has access to all of the features and functions in Automox. Users assigned to this role will have the ability to control your account and can manage billing, users, devices, and all patching operations. Full admins are also responsible for setting roles and permissions.

We have yet to find a piece of software that Automox has been unable to patch.

Jonathan Sibray //
University of Colorado Law School

Patch admin

Patch Admin users have the ability to control your devices, groups, and policies, with read-only access to other areas of the Automox platform. Users assigned with this role type are ideal for managing specific groups of servers or just patching operations, without having the ability to manage users or settings.

Patching is a thankless, redundant job that should be automated, which is why we chose Automox.

Jared Haggerty // CEO of Databerry

Billing admin

The Billing Admin only has the ability to change billing settings. These users are responsible for adding the corporate card or generating an invoice. Billing Admin users have read-only access to other pages and cannot change your patching and policy settings.

Having all my security status data centralized in one place makes my life a whole lot less stressful.

Corey Dolan // Tekside.IO

Read only

Users assigned with Read-Only access can only see what you have configured in Automox and do not have the ability to edit any settings or configurations. Read-Only users are ideal for generating reports or checking on patching status.

It just works. The client is easy to deploy and it is easy and intuitive to configure the policies.

Matthew Rehm // Methodist Theological School

Why Automox patch management?

Automox is leading the industry in building and delivering modern cyber hygiene solutions that provide the fundamental benefits needed to be confident in system security.

Endpoint hardening from a single console

Endpoint hardening from a single console

At under 10MB, the Automox agent can be deployed and utilized within a matter of minutes. Once the agent is installed, you can patch, configure, take inventory and report to all your corporate devices from a single interface, no matter the location or domain.

Quickly remediate vulnerabilities

Quickly remediate vulnerabilities

Automated policies and groups enable administrators to remediate vulnerabilities quickly across all their corporate devices. From “click, set, forget” automation to complete scheduling and workflow control, Automox results in incredible time savings, greater corporate security, and improved productivity.

Feature extensibility with Automox Worklets™

Feature extensibility with Automox Worklets™

Automox Worklets™ allow you to automate and enforce any scriptable action on endpoints regardless of location or domain, from software deployment to enforcing local configuration policies on an endpoint. If it can be scripted in PowerShell (Windows) or Bash (Linux and macOS), it can be automated across your connected corporate devices.