A company plans to create a Power Apps portal to manage support cases for customers. The company has an account hierarchy for customers. The hierarchy supports accounts, cases, and contacts where both contacts and cases belong to their relevant account.
The company has the following requirements:
✑ Portal users must only see the notes for the cases that they manage.
✑ Portal users must only see cases that are submitted by their colleagues.
You need to design the security model for the portal.
Which entity permission scope should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Box 1: Parent –
With Contact scope, a signed-in user in the role for which the permission record is defined will have the rights granted by that permission only for records that are related to that user’s contact record via a defined relationship.
Box 2: Account –
With Account Scope, a signed-in user in the role for which the permission record is defined will have the rights granted by that permission only for records that are related to that user’s parent account record via a defined relationship.
This scope means that the entity list will only show the records of the selected entity that are associated with the user’s parent account. For example, if an entity permission allows Read access to the Lead entity with the Account scope, the user having this permission can view all the leads of only the parent account of the user.
Self Scope allows you to define the rights a user has to their own Contact (Identity) record. Users can use entity forms or web forms to make changes to their own
Contact record linked with their profile.
Parental scope: In this most complex case, permissions are granted for an entity that is a relationship away from an entity for which an Entity Permission record has already been defined. This permission is actually a child record of the parent entity permission.