Every rule folder can either be contained within another rule folder, or have no parent (a "top-level" rule folder). Sub-folders and rules can inherit security from the parent folder or security can be explicitly set for each object.

Rule security defines the right to create, update, view, and delete a rule or rule folder.

• At run-time, security restrictions do not prevent users from executing these objects.

Security parameters can be defined separately for a folder and its rules. To access a rule, a user must have permission to access both the rule and the folder that contains the rule.

Sub-Folders

By default, sub-folders inherit the security of the parent folder. To view or modify the security of a folder, go to an application that contains the folder, select the folder, and use the Security option in the application contents grid toolbar.

The rights for each security setting are listed in the table below.

Actions	Administrator	Editor	Viewer	Deny
View the folder in the hierarchy	Yes	Yes	Yes	No
View rules and constants that reside in the folder (with sufficient permissions to the rule or constant)	Yes	Yes	Yes	No
Create new rules and constants in that folder	Yes	Yes	No	No
Update rules and constants that reside in the folder (with sufficient permissions to the rule or constant)	Yes	Yes	No	No
Delete rules and constants in that folder (with sufficient permissions to the rule or constant)	Yes	Yes	No	No
View the security of the folder from the application view	Yes	Yes	No	No
Update the security of the folder	Yes	No	No	No
Create sub-folders within that folder	Yes	No	No	No