Issue
How Permissions works in EBO
Product Line
EcoStruxure Building Operation
Environment
Building Operation Workstation
Cause
Software Permissions are used to control user activities in a software application. For example, permissions can be setup to manage the type of data and commands the user has permission to within a workspace, panel, or domain.
Resolution
EBO software permissions comprise path permissions and command permissions.
- Path Permission: Path permissions give a user or user account group basic permissions to the objects defined in a path. The permission level set on a path applies to all sub levels unless you set a new permission level for a sub level.
- Command Permission: To make the system even more flexible and useful, you can assign a user account group with special command permissions. Use the command permission to control exceptions from path permissions that allow or deny actions on specific commands. Command permissions will not restrict a user from specific properties of a given window. They function to remove items from Action or Right Click menus.
EBO 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.
- Download Software Permission.pdf, the detailed guide about how permission works in EcoStruxure Building Operation (Formerly known as SmartStruxure) and how to make it work.
- Check out the SmartStruxure Software Permissions Quick-Help video on the Exchange.
