Concept
Software Permissions
Software Permissions are used to control user activities in a software application. For example, you can set up these permissions to manage the type of data and commands the user has permission to within a workspace, panel, or domain. Software permissions comprise path permissions and command permissions.
If no software permissions are configured for a user account or its belonging user account group, the user has no access to Building Operation.
When creating a new user account, the account has by default no permissions to access Building Operation.
Any changes to a software permission settings of a user or user group are applied next time the user logs on.
Path Permissions
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.
For more information, see Path Permissions .
Command Permissions
To make the system even more flexible and useful, you can assign a user account group special command permissions. Use the command permission to control exceptions from path permissions that allow or deny actions on specific commands.
For more information, see Command Permissions .
Software Permission Rules
Software permissions provide members of user account groups with certain rights and privileges.
For more information, see Software Permission Rules .
Software Permissions and User Account Groups
A user account group can comprise both user accounts and other user account groups with similar interests. By using a well planned strategy for your user account groups, you apply software permissions and polices to multiple user accounts.
For more information, see Software Permissions and User Account Groups .
Software Permissions Summary
Similar to branches on a tree, software permissions direct users down a particular path in Building Operation. Along this path or branch, users can be granted permission to a set of read/write commands that control what they see and do. For example, an operator uses only a few objects on the WorkStation System Tree, such as Alarms and trend charts to acknowledge an alarm and survey the system. The operator has therefore access to those object, while other objects and commands that are not within the operator's responsibility are hidden.
Software Permission Rules
Assigning Software Permissions to a User Account
Assigning Software Permissions to a User Account Group
Editing the Software Permissions of a User Account
Editing the Software Permissions of a User Account Group
Removing Software Permissions from a User Account
Removing Software Permissions from a User Account Group
Command Permissions
Path Permissions
Software Permissions and User Account Groups
User Account Management Overview