Hi ShawnI have done this a few times. Owner teams within Power Apps and Dynamics should be considered any grouping of people, the structure of Teams and Business Units may resemble your organisation structure, but should not replicate it. I tend to add a choice column (option set attribute) to the Team table(entity). This provides the choice of something like "organisational", "functional", "security", this isn't necessary, but helps with admin. For this, I assume that each Account team could potentially be unique you may want to have an attribute of Account ManagementOwner teams work well for when records are reassigned, but sometimes need a bit of help for when new child records are created.There is a limitation of using ONLY owner teams for this, which isn't clear whether this would be an issue: If different users need different levels of access to the child records, then they cannot have any access to other account and child records.
For exampleRole 1, is able to createRole 2 is able to create and editRole 3 is able to create, edit and deleteThese roles role would have the varying privilege for the account and it's child records at BU, PC or ORG level, EXCLUDING read and assignRead and Assign at user level would be assigned to the team owning the account. The layering of these roles would provide the necessary access.However, if users do need limited access to some other accounts/child records, then the members of a specific account team would all need to have the same access to those records.
I imagine the difficulty may come to the Account entity itself... eg everyone can read all accounts, but only Account Managers can edit the accounts for which they are in the team for - this may then be a use case for a share (either to user or access team).Hope this helpsJamie
If you've found this thread useful, dive deeper into User Group community content by role