ClearSCADA

In ClearSCADA, security is designed to act in a hierarchical manner such that permissions are inherited from parent groups to their descendant objects. As required security may be explicitly defined on individual objects (including groups) within the database and these settings will be inherited by any descendant objects. By default new objects are configured to inherit permissions form their parent object and as such the "Inherit Permissions From Parent" check-box will be selected.

It may be desirable to configure some areas of the ClearSCADA database with specific permissions. This can be done through the security setting of a group by deselecting "Inherit Permissions From Parent" and explicitly defining the required permissions. These permissions will be inherited by all descendants that have "Inherit Permissions From Parent" selected.

When allocating permissions it may be desirable to force all descendants inherit the same permissions regardless of whether any of them previously had explicit permissions defined. This can be achieved by selecting "Replace Permissions on Descendants". Using this feature ensures that all the objects (including sub groups) will inherit these security settings by re-setting "Inherit Permissions From Parent" on all descendants.

For more information on security, refer to the online help 'Guide to Security'.

This information is current for ClearSCADA 2007 R1
  1. Mar 28, 2010

    Adam Woodland says:

    > Using this feature ensures that all the objects (including sub groups) will...

    > Using this feature ensures that all the objects (including sub groups) will inherit these security settings by re-setting "Inherit Permissions From Parent" on all descendants

    This excludes instances which don't have their ACLs property overridden in the corresponding template. These return an error.