@AshishR6

I guess you are speaking about node level data pages where we provide access group for load authorization. This access group is used by the node level Dpages to access the desired application to invoke the load activity. This access group configuration is not related to operator ID. Operator ID with any access group can open and see the Dpage, but when the Dpage loads it will use the specified access group mentioned in the load authorization block.

For further clarification refer to the below link.

https://support.pega.com/question/why-we-need-access-group-node-level-data-page

@AshishR6 A DP is created inside a ruleset, so every operator that has access to that ruleset is able to use that DP (in normal conditions). Nothing has to do with the access group defined in the Node-Level DP.

The access group defined in a Node-Level DP is relevant when loading the DP in runtime. For thread and requestor-level DPs, they will use your current requestor access group, but for Node-Level, since it is not attached to any operator, it needs an access group to know which rulesets are available during the DP loading.

@AshishR6  

If a Data Page is created using the abc access group, then users with the abc access group can use it because the Data Page is part of their application. But if a user has the bcd access group, they can use the Data Page only if the ruleset that contains the Data Page is also available in their application. Access to a Data Page is not controlled just by the access group name it depends on whether the user’s application includes the correct ruleset and version where the Data Page is defined. So, if the bcd application does not have the ruleset where the Data Page is created, the user will not be able to see or use it. Make sure the ruleset is shared across applications if you want both abc and bcd users to access the Data Page.