PRTG Granular Access Control: A Workaround for Access Rights Limitations

PRTG Access Rights: Solving the Granularity Gap Without Compromising Control

Does PRTG support granular access control?

PRTG does not natively provide granular, action-level access controls. Its permission model uses no access, read, write and full access, which can mean granting technicians broader permissions than they need simply to perform tasks such as pausing sensors. This article explains the limitation and a practical workaround for introducing greater control.

For sys-admins and IT leads, Paessler PRTG Network Monitor is a powerful and widely adopted monitoring solution. But despite its strengths, one recurring challenge continues to frustrate technical teams: PRTG access rights are simply not granular enough.

PRTG access rights, out of the box, offer only four permission levels at the group level:

• No access
• Read access
• Write access
• Full access

This simplicity can be helpful, but it also creates a recurring pain point: lack of granular control. For many teams, this limited model creates several operational challenges.

PRTG Access Rights: Limited Granularity in Device-Level Access Control

While PRTG does allow access rights to be configured at the device level, typically by organising devices into dedicated groups, the core issue lies in the lack of fine-grained permission options. Once a user is granted write access to a device or group, they gain broad control over all associated settings, including the ability to pause sensors, modify thresholds, acknowledge alarms indefinitely, or even delete devices.

This creates a challenge for teams that need to delegate specific operational tasks, such as pausing a flapping sensor or adding a notification, without exposing critical configuration controls. The absence of role-based privilege separation (e.g., operator vs. administrator) means that even routine maintenance actions require elevated access, increasing the risk of accidental or unauthorised changes.

PRTG Access Rights: Write Access Unlocks Too Much Power

In real-world environments, devices don’t always fail cleanly. They flap, bouncing between up and down states, and each transition can trigger a new alert. These alerts often integrate with helpdesk systems, resulting in multiple redundant tickets and unnecessary noise.

The logical fix is to pause the sensor temporarily, allowing the issue to stabilise. But here’s the problem: PRTG doesn’t allow you to grant pause rights without also giving users broader write permissions. That means technicians who need to pause a sensor can also change thresholds, disable alerts, or make other configuration changes, often unintentionally.

We’ve seen teams try to work around this by:

• Granting write access and manually auditing sensor configurations.
• Using scheduled scripts to resume sensors from “banned” states.

These methods help, but they’re far from ideal, especially in environments where PRTG Access Rights need to be tightly controlled.

This lack of granularity in PRTG Access Rights forces teams into a difficult trade-off between operational flexibility and configuration control.

PRTG Access Rights: Limited Role-Based Privilege Separation 

PRTG offers predefined roles, including read-only, read/write, and administrative access, but the challenge lies in the limited configurability within these roles. For example, the “read/write” role allows users to pause sensors, which may be necessary for service desk teams, but also enables them to modify thresholds, acknowledge alarms indefinitely, or delete devices.

Similarly, the “read-only” role may allow acknowledging alarms but not pausing them, which might be acceptable in some environments but not in others. There’s no built-in way to customise or fine-tune these privileges, to suit specific operational requirements, such as allowing a user to add notifications without editing sensor configurations.

This rigidity in PRTG Access Rights makes it difficult for IT teams to implement safe, scalable access models that reflect real-world responsibilities across different roles.

You can view the Access Rights Management | PRTG Manual here.

Our Solution: A Smarter Way to Manage Visibility

As a PRTG Enterprise Partner, we’ve been using, implementing, and supporting PRTG for over a decade. Over time, both our internal teams and clients have encountered the same frustrations with the limitations of PRTG Access Rights, particularly around the lack of granularity and role-based control.

To address these challenges, we’ve developed a custom workaround that helps restrict what users can see and interact with in the PRTG interface, without modifying the underlying access rights model. This approach allows teams to maintain operational flexibility (such as pausing sensors when needed) while reducing the risk of unintended configuration changes.

Our solution is designed to be non-invasive, scalable, and adaptable to environments where read/write access is necessary but needs to be tightly controlled. While it doesn’t change PRTG’s native permission structure, it provides a practical layer of control that enhances usability and governance. Explains Paul Edwards, Head of SOC

Is Our Solution Right for Your Team?

If your technicians already have read/write access and you’re looking for a way to limit what they can see or interact with, our workaround approach is a viable enhancement to your PRTG Access Rights strategy. However, if your users are strictly read-only and don’t need pause functionality, this solution may not be necessary.

While it doesn’t change PRTG’s native permission structure, it introduces a practical layer of control that helps prevent accidental actions like indefinite acknowledgements or threshold edits.

It’s not foolproof, technically savvy users could bypass it, but compared to the alternative of granting full write access, it offers a safer and more controlled experience for operational teams.

Need Help Optimising Your PRTG Access Rights?

As a PRTG Enterprise Partner, we specialise in helping mid-enterprise teams customise and secure their PRTG environments. Whether you’re struggling with access control, sensor management, or interface usability, our team of experienced PRTG technical consultants can help.

Contact us today to learn more about our PRTG professional services and how we can tailor a solution to your environment.

PRTG Access Rights FAQs

Can you configure granular access rights in PRTG?

PRTG provides four main permission levels: no access, read access, write access and full access. While permissions can be applied at group and device level, PRTG does not natively provide granular control over individual actions within those permission levels.

Can you allow a PRTG user to pause sensors without giving them full write access?

Not natively. Users who need to pause sensors generally require write access, which also gives them permission to perform other actions such as changing thresholds, modifying settings or deleting devices. This can create challenges when delegating monitoring tasks to service desk or operational teams.

What is the difference between read and write access in PRTG?

Read access allows users to view monitoring information with limited interaction, while write access enables users to make changes within PRTG. The challenge is that write access can provide considerably more control than a technician needs for routine tasks such as pausing a sensor.

How can you improve role-based access control in PRTG?

Where PRTG’s native permissions do not provide sufficient granularity, additional controls or customisation can be used to restrict what users can see and interact with. Krome has developed a workaround that adds an additional layer of control while retaining the underlying PRTG access model.

How can you prevent accidental configuration changes in PRTG?

Organisations can reduce the risk of accidental changes by limiting elevated permissions, controlling which interface options users can interact with and regularly reviewing access. Where technicians require write access for operational tasks, additional controls can help restrict unnecessary configuration changes.

Can PRTG access rights be customised for service desk teams?

PRTG’s native roles have limited customisation, which can make it difficult to give service desk teams access to specific functions without providing broader permissions. A customised approach can help teams retain functions they need, such as pausing sensors, while reducing access to unnecessary configuration options.