2145780

Author: tapanm-MSFT

powerapps-docs/maker/portals/configure/entity-permissions-studio-walkthrough.md

@@ -56,6 +56,17 @@ Contoso has the following relationships configured between tables in Dataverse.
 - **Contact (One) to Car listings (Many)** - One sales staff (contact) can have multiple car listings.
 - **Dealership (One) to Car listings (Many)** - One dealership can have multiple car listings.
 
+### Customizations
+
+Contoso has the following customizations configured for this scenario.
+
+- Web pages have table permissions enabled. More information: [Manage page permissions](webpage-access-control.md)
+- Web pages have [lists](entity-lists.md) configured with the tables, views, and the ability to create/view/edit/delete records as appropriate.
+    - To show [all car listings to all authenticated users](#view-all-car-listings), the web page has list with a view from the **Car listings** table with only View record permission.
+    - To show, update, and delete [owned car listings](#view-update-and-delete-owned-car-listings), the web page has list with a view from the **Car listings** table having View, Create, Edit, and Delete records permissions.
+    - To show [all car dealerships](#view-all-car-dealerships), the web page has list with a view from the **Dealerships** table having View, Create, Edit, and Delete records permissions.
+    - To show [car listings for an associated dealership](#view-car-listings-for-associated-dealership), the web page has a list with a view from the **Dealerships** table. This list can be used to view the dealership details, with view having subgrid that shows the car listings associated to the selected dealership with View, Create, Edit, and delete records permissions.
+
 ## View all car listings
 
 Contoso has a web page with a basic form that shows all current car listings in the inventory to all authenticated users.

powerapps-docs/maker/portals/configure/entity-permissions-studio.md

@@ -22,11 +22,12 @@ Portals Studio shows four different **Access types**. Depending on the access ty
 
 1. **Global access** - Applies the selected table permission and privileges to the users from the selected roles for *all records*.
 1. **Contact access** - Applies the selected table permission and privileges to the users from the selected role *associated to the signed-in user*.
-1. **Account access** - Applies the selected table permission and privileges to the users from the selected role *associated to the signed-in user's parent account*.
+1. **Account access** - Applies the selected table permission and privileges to the users from the selected role *associated to the signed-in user's account*.
 1. **Self access** - Applies the selected table permission and privileges to the users from the selected role *for only their own contact record*.
 
 > [!NOTE]
-> **Parent scope** is only available in the Portal Management app. Instead of creating a table permission with the access type as **Parent**, directly add or associate child permission to existing table permissions when using portals Studio.
+> - **Parent access type** is only available in the Portal Management app. Instead of creating a table permission with the access type as **Parent**, directly add child permission to existing table permissions when using portals Studio.
+> - Ensure you enable table permissions on web pages for permissions to take effect. More information: [Manage page permissions](webpage-access-control.md)
 
 ## Configure table permissions using portals Studio
 
@@ -165,7 +166,7 @@ To add a child permission to an existing table permission using portals Studio:
 
     1. Table - table that the child permission is for.
 
-    1. Access type - relationship between the table for primary table permission, and the selected table for the child permission.
+    1. Relationship - relationship between the table for primary table permission, and the selected table for the child permission.
 
     1. Privileges - grant privileges for the child permissions.