Service Writer role makes entities for contacts unaccessible

(1) Share

Report

Posted on by AnnaC_25

Hello Community..

I have this curious case with power portals and roles of users..

When a user with Service Writer role creates an entry in the db (with the corresponding Account column relationship) , the contact signing in from the power pages , although being in the account relationship, he cannot access the infos published for this entity in the pages..

When a user with Service Admin role does the same the contact can access it...

1. Is there a reason behind why?

2. What roles can I make the user that creates the entries in db in order for the signed in contact to access it from the power pages...

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

Sort by

WeiguangX 12 on at

Like (1)

Report
Copy link

Link copied!

I think table permission is the problem. Are both roles in the same permission? Or is the same relationship being used in both table permissions?

Was this reply helpful? Yes No
PT D365 on at

Like (1)

Report
Copy link

Link copied!

HI WeiguangX

So in our case we are utilising same Contact , so every portal user will have self access. But for certain user, they need to get access for editing other contact details. My concern is to avoid giving Organisation level access , to contact for Type 2 users, and try to restrict in Liquid template.

Was this reply helpful? Yes No
Suggested answer

Fubar 8,487 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Just picking up on this comment "My concern is to avoid giving Organisation level access" - if you are not already aware Power Pages does not use the Dataverse Security model (where you would have BU and Organization level access etc), and uses Table Permissions instead (Where there is no BU level access but has scopes of self, Contact, Account, Parent and Global).

Also, be aware that records created or updated directly in Dataverse (not as a primary record from Power Pages) will not surface to the portal directly and are subject to the portal's caching mechanism (which whilst usually updates within a few minutes the Microsoft SLA is actually 15 mins) - so if you have records that are not available until a number of minutes later in the portal one possible reason may be due to the portal's cache.

Was this reply helpful? Yes No