Question
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Barclays UK PLC
GB
Last activity: 16 Mar 2016 0:51 EDT
Denial of Access to Ruleset
Can we deny the access of an operator to a particular ruleset? If yes, How?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Pegasystems
US
No. You would need to make a new rule-application that omits ruleset X. Refer the new access group to the rule-application. Make sure the rule-application refers to only a chain of other rule-applications that do not have ruleset X.
Then the operator will not have access to ruleset X.
NOTE:
To keep things re-usable, you can have a rule-app with just X in it that refers to all the other rule-apps. The restricted operator's access group would refer only to those other rule-apps while the non-restricted operator's access group would refer to rule-app with just X in it (which, as mentioned, refers to all the other rule-apps).
/Eric
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Pegasystems Inc.
IN
- would it be convincing to request to associate the operators by creating a new application, access group to restrict??
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Barclays UK PLC
GB
Well, the application is already existing. For few reasons, one or more rulesets are needed to be accessed by few developers only. We can secure the ruleset by setting a password which would be equivalent. But, my seniors seek something which can deny the access of a particular Operator to an existing ruleset.
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Pegasystems
US
If you give that operator an access group whose chain of rule-applications does NOT contain ruleset X, then the operator will be denied access to ruleset X. /Eric
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Barclays UK PLC
GB
Hey Erik Thanks for replying. Is it really possible to define an access group with not involving a ruleset X however the ruleset X is a part of an application defined in the access group?
Accepted Solution
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Pegasystems
US
No. You would need to make a new rule-application that omits ruleset X. Refer the new access group to the rule-application. Make sure the rule-application refers to only a chain of other rule-applications that do not have ruleset X.
Then the operator will not have access to ruleset X.
NOTE:
To keep things re-usable, you can have a rule-app with just X in it that refers to all the other rule-apps. The restricted operator's access group would refer only to those other rule-apps while the non-restricted operator's access group would refer to rule-app with just X in it (which, as mentioned, refers to all the other rule-apps).
/Eric
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Barclays UK PLC
GB
oh ok Eric thanks