@KOMARINA

I expect that any user who has App Studio access to the same application as you will be able to edit the records on the data type. The configuration you've depicted in your settings is to name a group of end-users who are authorized to modify the records. This plugs into Pega's Delegated rules capability which determines what is visible on the Manager channel (portal).

So take this HR Application (in 8.5, I know your question was tagged as 8.4.2) which has an Employee data type, the records of which only Hiring Managers are authorized to modify:

I've also set up (via the Users / Access path in App Studio) the Candidate and Hiring Manager personas (Access groups) to come into the Manager portal:

When a Hiring Manager logs into Pega, they get the Manager channel portal showing the Employee data type via the Configuration landing page:

... and when they click Edit, they can edit records:

When a Candidate logs into Pega, they also get the Manager channel, but no Configuration landing page is offered in the left menu, as this Personal has not been chosen to edit records for any of the data types:

This shows the effect of the configuration on the Data Type settings in App Studio.

Here are the links to the 8.4 documentation about these settings:

• https://community.pega.com/sites/default/files/help_v84/express/procomhelpmain.htm#data-integration/data-types/dm-delegating-a-data-type-tsk.htm
• https://community.pega.com/sites/default/files/help_v84/express/procomhelpmain.htm#designer-studio/delegating/cm-modifying-a-delegated-item-tsk.htm

I hope this answers your question.