Power Platform Community Forum Thread Details

Hello Everyone,

Good Day,

My Work:

1. I have (n) number of tables with 'user' privilege on records.

2. I am creating a Entra ID security team in my dataverse environment 'Team' and add set off users.

Note: certain users can be part of multiple security teams.

3. When a user creates a record in Canvas application, I am triggering a cloud flow to share the access of that record (using their account information) to the team they are part of and if the user is in multiple teams in the same flow i am sharing that record (Read,W,D) to those teams as well

Note: As sharing of records for most tables happens only within the team, there are only 1 or 2 tables where that records should be visible to multiple team certain users are part of.

Problem:

1. The records of the tables,that should be shared to multiple teams aren't being displayed even after I check the access of those records and it displays that it was shared to that team.

What I tried: used webapi to check the records as one of the team member -> not showing.

Verified from the users end too -> not showing.

2. But, all the records for those tables that are supposed to be shared within the team only are working fine.

Note: This happens for users who are part of multiple teams and the records those should be visible across teams causes an issue (even after sharing those records and verified from check access that i was shared to them) not the ones who are just part of single team.

My expectation in answer:

1. Is it sort of a power platform issue? That it shows it is shared but the team members can't access it?

2. If no then an answer without changing core application development structure.

Categories:

Building flows

It looks like you’re experiencing an issue where records appear to be shared to multiple teams but aren’t visible to users who belong to more than one team. That usually points to Dataverse security model nuances, not a literal “sharing bug.” When a user is part of multiple teams, access checks evaluate all security roles and team memberships, and sometimes inherited privileges don’t apply as expected if a user’s effective permissions don’t include the necessary Read/Write access on that table.

A few things to try:

Verify the user’s effective permissions using the Check Access Web API for each team context to ensure Read/Write privileges are truly granted.
Ensure the security roles assigned to each team actually include the required privileges on that table.
Consider using hierarchy or owner-based sharing instead of team-based sharing if your model is complex, as this often yields more predictable results in multi-team scenarios.
Also double-check that the flow making the sharing call is running under a user with sufficient privileges — Dataverse doesn’t elevate rights automatically. Approaches like these usually help resolve these kinds of visibility gaps.