Concept
Relative Path Permissions Rules
You set permissions on a relative path twice.
First, you set permissions on the objects in the template. Objects in the template can be granted the following path permissions: Read, Write, Create, Delete, Edit, Force and Command.
Second, you set permissions for user accounts and user account groups. A user account or a user account group can be granted the following path permissions: Read, Write, Create, Delete, Edit, Force and Command.
|
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.
Relative Path Permissions