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.
The following permissions can be set for a path:
No Access: Users cannot navigate to or modify any of the objects in the path.
Read: Users can navigate to the objects but cannot modify them.
Full Access: Users can navigate to and modify the objects.
Example
A user has the permission Full Access to the folder Building A. The user account group also has Read permissions to the folder Building B, but No access to the subfolders of Building B. Therefore the user has permission to navigate and modify the objects in the Building A folder, but only permission to view the objects in the Building B main folder.
action_zoom_plus_stroke
Figura:
Path permission levels in Building Operation
Path Permissions Example
A user account group has the permission Full Access to the Enterprise Server and No Access to the Servers folder on the Enterprise Server. A single user account has Full Access permissions to Automation Server 1, but No Access to Automation Servers 2 and 3. The No Access permission on the Servers folders makes it possible to give specific user accounts access to specific Automation Servers in that folder.
Per maggior informazioni, consulta Path Permissions Example
.
Context-Sensitive Path Permissions
You can manage permissions by configuring the permissions for a given user account or user account group to a certain object in the System Tree pane or List View and below that object, for example, a folder and its contents.
Per maggior informazioni, consulta Context-Sensitive Path Permissions
.