Usually, if below conditions are met, Private edit button should be available even if the ruleset is locked.
- "Allow rule checkout" in "Security" tab of operator record is checked
- "Use check-out?" in "Security" tab of ruleset record is checked
- Access Group of user has "pxAllowPrivateCheckout" privilege
If Developer A login using default authentication, Developer A is able to private edit the rules in locked ruleset.
If Developer B login using custom authentication, Developer B does not see "Private edit" button, hence developer B cannot private edit the rules in locked ruleset.
Is there anything I need to consider in order to allow private edit, when using custom authentication? It might not be because of authentication, but this is only the difference I see until this point.
***Edited by Moderator: Pallavi to update platform capability tags***
Can you trace the two logins to compare? When I log in, I see the Code-Security.InitialProfileSetup activity is invoked and calls SetAllowCheckOut, which sets a value to determine whether users may check out rules.
@CarissaW_GCS I took a look at a tracer log while the authentication activity is running and confirmed that Code-Security.InitialProfileSetup is running. Seems like SetAllowCheckOut ran successfully and "pyAllowRuleCheckOut" is set to "true"