Question

A logistics company uses model-driven apps on Dataverse. A group of 12 dispatchers needs collaborative ownership of a set of 'Route' records so that any dispatcher can edit records the others create, and so that reassigning work between dispatchers requires no manual record re-sharing. Managers outside the group should have read-only access. The developer wants the lowest-maintenance approach that survives staff joining and leaving the group. Which design should the developer implement?

Accepted Answer

Set the Route table to User or Team ownership, create an owner team for the dispatchers, and assign Route records to that team; grant managers a security role with Read at the business unit level.

Answer

Set the Route table to User or Team ownership, assign each Route record to an individual dispatcher, and use record sharing to share each record with the other 11 dispatchers.

Answer

Set the Route table to Organization ownership so all users automatically have the same access, then restrict managers with a custom business rule.

Answer

Create a business unit for the dispatchers, move all 12 users into it, and rely on the default business-unit-scoped security role to grant editing.