Hi Satish,

The Managed Access roles created dynamically to facilitate Persona's feature in App Studio and mapping Channels & Pages in App studio to a particular persona will create ARO's inside these managed access roles. 

Creating Persona's - https://community.pega.com/sites/default/files/help_v84/express/procomhelpmain.htm#app-dev/creating-personas-tsk.htm  --- Creates Managed Access role name 

Granting Access to  Persona - https://community.pega.com/sites/default/files/help_v84/express/procomhelpmain.htm#testdrive/roles/tsk-addingarole.htm -- Include ARO's into Managed access role name.

If you don't intend to develop your application in App Studio, you may ignore this checkbox and leave it as default (Unchecked). 

Let me know if that clarifies!

Please find the below article which might be helpful.

https://community.pega.com/knowledgebase/articles/application-development/84/understanding-project-roles-and-personas

Hi Satish,

If you select the Is manageable in App Studio checkbox, the system automatically selects the Stop access checking once relevant Access Role to Object instance explicitly denies or grants access checkbox. Therefore, ensure, that the order of roles listed under the checkboxes is correct.

Please check the below article for more info

https://community.pega.com/knowledgebase/articles/pega-sales-automation/configuring-role-based-page-access-app-studio

https://community.pega.com/sites/default/files/help_v83//express/procomhelpmain.htm#ui/ui-landing-pages/ui-configuring-role-based-page-access-tsk.htm

Thanks

Siddharth