Suggested by Sam Woodhouse – New
Currently, the main way to apply wider permissions to records within Dataverse is by utilising business units and enabling users to create records that can be seen and updated by their business unit. This model doesn't always fit with implementations where users are across multiple business units in the organisations. If there are no business units in place you could utilise them in your environment but then you've locked that environment down to only utilise your structure, if in a shared environment another developer wants to build an organisation-wide application that utilises the organisational structure for security this can no longer be done since a different app is using a different structure to emulate what could be done more simply using Dataverse Teams.
What would be more beneficial, is if I could specify a security role for custom entities that users across multiple teams need to access and specify that the created records are available to all Dataverse Team members. These Team members can be controlled via AAD security groups and allow for a much easier way for data segregation (at least for those of us not utilising Dynamics) for teams of users that don't sit in a standard business unit approach.