Power Pages: Security - How to configure table permissions with Connections

Authenticated Pages users are technically Dataverse contacts, and their table permissions to view data will depend on their contact's relationship to the records they are attempting to view. The beauty of Pages is that you can repurpose the relationships and objects that you already have in Dataverse... but what if your tables are using Connections to relate the records to Contacts, instead of a direct relationship?

In this scenario, Contoso is a B2B professional services organization. Contoso has an internal website and they only want their Pages users to see Accounts for which they are designated as Account Team Members on. In the model-driven app, rather than having a Contacts subgrid to reflect these relationships, the Account table has a Connections subgrid given that Contoso uses a combination of Users and Contacts.

The following steps assume that you already have created the necessary Pages objects, which include at bare minimum, a web page, web role, and list.

How to set the table permissions:

Permission #1, Connection level

1. From Pages Studio, navigate to Security > Table permissions > New permission
2. Name it Contact Connection
3. Set the table to Connection
4. Access Type to Contact access
5. Relationship to contact_connections1 (Connected From)
6. Permissions to at least Read.
7. Specify your web role. 
8. Save

Permission #2, Account level

1. Add a child permission
2. Name it Contact Connection > Account
3. Set the table to Account
4. Relationship to account_connections2 (Connected To)
5. Permissions to at least Read.
6. Specify your web role.
7. Save.

Expected behavior

When one of the Contacts from the Connections subgrid on the A. Datum Corporation account record signs into the website, they will be able to see the accounts that they are related to via Connection.

Skylar Shonblom