Dynamics Community Forum Thread Details

Team Based Routing

Hello Community,

I am building a Model-Driven Power App on Dataverse with team-based record visibility and multi-tier approval routing. Views and security roles are already in place. Approval functionality is also done. There are over 50 teams, and each team has one submitter and 4 approvers.

Visibility Requirements:
∙Submitter → sees all records from their team
∙Approvers (4 tiers) → sees records pending their specific approval stage AND all team records in the main view
∙No role should see records outside their own team

Questions:
1.Is setting owning team at submission the correct way to restrict cross-team visibility in Dataverse, or should Business Units be involved?
2.Is using a current approval tier field updated via Power Automate the recommended way to drive stage-specific views, or is there a better pattern?
3.With multiple security roles on one team, how should role privileges be configured so each role only sees records at their stage?
4.Any best practices for managing role-specific views tied to approval stages in a Model-Driven App?

Thank you!