Guidance Needed for Table Permissions in Power Pages

(2) Share

Report

Posted on by skolarvs

Hi Team,

I need help with the following scenario:

I have a custom Partner table, which has a 1:N relationship with the Contact table—each Partner can be linked to up to four Partner Contacts.

Requirements:

When a Partner Contact logs into the Power Pages portal, they should only see the Partner record associated with them.
Additionally, they should be able to view all Cases linked to that Partner (regardless of which Partner Contact created the Case).

Constraints:

I cannot use the Account table for Partner, so the Account Access Type option in Table Permissions is not applicable.

Could you please advise how I can achieve this setup in Power Pages?

Your quick assistance is greatly appreciated.

Categories:

Power Apps portals

I have the same question (0)

All responses (4)

Answers (0)

Lucas001 2,429 Super User 2025 Season 2 on at

Like (0)

Report

Hi @skolarvs,

question would be if you want to be sure that others cannot see data in the default view or would be a quite large fetchQuery for XML be enough?

They Partners would still need read access to the table. Otherwise you would need to create your datamodel in a different way I believe.

In your case you would need certain records owned by the user so you can use the self access permission.

This one could than be linked to the Cases Table so that you get the metadata of that table.

Was this reply helpful? Yes No
skolarvs 67 on at

Like (0)

Report

@Lucas001 - I want Partner Contacts to have visibility into all records created by other Partner Contacts associated with the same Vendor.

Example:

Vendor Contact Vendor

User 1 Vendor A

User 2 Vendor B

User 3 Vendor B

User 4 Vendor A

For example, when User 1 logs into the portal, they should be able to see Case records associated with both User 1 and User 4, provided both are linked to Vendor A. Essentially, both User 1 and User 4 should have access to the same set of Case records for Vendor A.

This shared visibility should be reflected consistently on Power Pages.

Was this reply helpful? Yes No
Suggested answer

Nafiun2120 124 on at

Like (2)

Report
Hi @skolarvs

Great question and clear scenario! Based on your requirement—where multiple Partner Contacts should be able to view all Cases associated with the same Partner (custom table)—you can achieve this setup using a Web Role + Table Permissions + Related Table access control. Here's a suggested approach:

1. Table Relationships:

Partner (custom table) → 1:N → Contact

Case → N:1 → Partner

2. Table Permissions Setup:

Table: Partner

Permission Type: Global Read

Access Type: Use a custom Web Role tied to authenticated users

Purpose: Allow Contacts to retrieve the Partner record they belong to.

Table: Case

Permission Type: Read

Access Type: Parent - Partner

Purpose: Ensures that all users related to the same Partner get access to Cases linked to that Partner, regardless of which Contact created it.

3. Web Role:

Create a custom Web Role like PartnerUser

Assign it to the authenticated Partner Contacts

If this helped, please mark it as an answer and give it a Like to help others in the community too!

Was this reply helpful? Yes No
Suggested answer

surya narayanan 102 on at

Like (0)

Report

Hi,

Your Data Model
Partner (custom table)
Contact (OOB table)

Each Partner → up to 4 Partner Contacts (1:N relationship via a lookup partnerid on Contact)

Case (OOB table)
Linked to Partner via a lookup (partnerid)

Requirement
When a Partner Contact logs in:
They see only their Partner record.
They can also see all Cases for that Partner, even those created by other Partner Contacts.

Why Table Permissions Don’t Work by Default
Table Permissions work great with the OOB Account table because of the "Account Access Type" option, but your Partner table is custom.
You can still achieve the same behavior by using Table Permissions with Relationship paths.

Solution
Step 1. Create Table Permission for Partner
Go to Portal Management → Table Permissions → New.

Table: Partner
Access Type: Contact
Scope: Parent
Parent Table Permission:
Create a Table Permission for Contact:

Table: Contact
Scope: Self
Give Read privileges.

Use this Contact table permission as the Parent of your Partner permission.
Add the relationship filter:
Relationship: partnerid (the lookup on Contact that links to Partner).
Result: Logged-in contact can only see the Partner linked via their partnerid.

Step 2. Create Table Permission for Case
Table: Case
Scope: Parent
Parent Table Permission: Select the Partner table permission created above.
Set required privileges (Read, Append, etc.).
Result: Any Case linked to that Partner will be visible, regardless of which Partner Contact created it.

How it Works
Portal authenticates the user as a Contact.
Contact table permission (Self scope) grants access only to their own Contact record.
Partner table permission (Parent scope) uses the partnerid lookup to give them access to the Partner record linked to their Contact.
Case table permission (Parent scope) uses the Partner table permission to give access to all Cases associated with that Partner.

Why This Works
Access cascades: Contact → Partner → Cases.
No need to use Account or "Account Access Type".
Supports your 1:N relationship (one Partner, up to four Contacts).

Optional: Show only one Partner
If a Partner Contact can only ever belong to one Partner, this is automatic.
If a Contact could belong to multiple Partners, you’d need a many-to-many table permission path.

Was this reply helpful? Yes No