Primary User Group

The primary group is basically just the group that comes first in the alphabetical order of the groups. Read/Write permissions always outweigh read permissions. That said, if the user is within a group that has r/o permissions for an object, but is member of a group with r/w permissions for an object, he should be able to modify that. Can you check that out? :)

Is this still the case in the latest stable release (18.1.37.xxxx)

Hi Craig,

What exactly are you referring to?

Kind regards,
Stephan Linke, Tech Support Team

Similar question (although this is about 'Read' vs 'None', not 'Read' vs 'Read/Write'):

User is member of multiple groups in PRTG (via connected AD groups).

On specific sensors:
One group has Read rights, the other group has None rights (chosen for giving groups None rights, to keep their PRTG view clean; them not seeing sensors they're not responsible for).
Resulting permission on this sensor for this user: None

Within PRTG, is 'None' overwriting 'Read'?
Because it doesn't look like PRTG is using 'least restrictive'...

Hi Corné,

I'm not sure I'm following here. What you have interconnected in AD is one thing, inside PRTG an AD user cannot be member of several groups, only one AD connected group. The access rights configured for that group the user has been "linked" to upon first successful AD login, determines the user's access rights as configured in the tree for each object.

Or maybe I'm misunderstanding something here, please let me know, I can never rule that fully out :)

Kind regards,

Erhard