Software permissions provide members of user account groups with certain rights and privileges.
Building Operation uses the following basic rules to interpret software permission priorities:
The path permission settings of lower branches overrule the settings of higher branches within a user account group.
For example, a user account group has the Read permission to the path /Trend_Logs and Full Access permission to the subbranch /Trend_Charts. Users in the user account group have permission to modify the objects in the /Trend_Charts but can only view the objects in the superior /Trend_Logs.
If the path /System has the permission level Read, and the subbranch /Alarms has the permission level Full Access, the users in the group have full access to the objects in the /Alarms path.
The highest permission rule wins between user account groups.
For example, if a user has inherited the permission to accept an alarm from one group, this overrules settings from other groups that deny the user the permission to acknowledge alarms.
The software permissions for a single user account overrule the permissions of any inherited user account group permissions.
The path permission rules also apply to the basic commands Create, Copy, Paste, Cut, Move, Rename, and Delete. For example, you only need the Read path permission level to copy an object but you need the Full Access path permission level to paste an object. See the table for more details.