You manage software permissions by combining various types of permissions.
By using a well-planned strategy of assigning software permissions, you can optimize performances of the users. You can also apply your policies to control exploitation of the EcoStruxure BMS.
Property |
Description |
Read |
Permits viewing and listing path content |
Write |
Permits an administrator to change configurations except for bindings, programs, and graphics |
Create |
Permits creating new objects on the path |
Delete |
Permits deleting objects under the path. Delete permissions are required on a folder to delete its contents |
Edit |
Permits editing objects on the path |
Force |
Permits forcing values on the path |
Command |
Permits the execution of commands on the path. Command permissions can override this permission for specific commands |
Inherited |
Indicates that the permissions are inherited from the parent folder |
You need delete permissions to rename, paste and duplicate folders and objects in EcoStruxure Building Operation software.
You can always edit graphic and program objects in the relevant editor, however in order to save it on your server you need "Edit" permissions. You can save your edits on your hard drive or export to a location of your choice even if you don’t have “Edit” permissions.
Building Operation software uses basic rules to determine software permissions priorities.
Command permissions of a user account are inherited from the most advanced permissions in any group the user belongs to. The command permission Allow overrules Deny , and Deny overrules No Setting .
Example. Paul belongs to Janitors and to Administrators. Janitors does not have permission to accept an alarm, but Administrators have. Paul inherits the permission to accept the alarm from Administrators.
Relative path permissions configured for an individual user account overrule permissions inherited from user account groups.
Type permissions overwrite path permissions.