The security model is the part of a Dynamics 365 implementation that’s hardest to change later. Get it wrong and you’ll pay for it in performance problems, support tickets and uncomfortable audit findings.
Start from the operating model
Before opening the admin centre, map how the organisation actually works: regions, branches, segments and the people who need to see across them. The business unit hierarchy should reflect data ownership, not the org chart.
Keep roles composable
Rather than one giant role per job title, build a small set of base roles and layer capability roles on top:
- A base role grants the minimum needed to use the app.
- Capability roles add specific rights, such as approving a complaint or exporting data.
- Users get a combination that matches their job.
This keeps roles understandable and makes access reviews far easier.
Use teams deliberately
Owner teams and access teams solve different problems. Owner teams are ideal for shared queues and departmental ownership; access teams handle record-by-record collaboration without exploding the number of roles.
Test it like code
Security changes should move through environments like any other customisation — in managed solutions, with test users for each persona and a checklist of what each one should and shouldn’t see.
Bulk changes need tooling
When hundreds of users need a role assigned or removed, clicking through the admin centre doesn’t scale and isn’t auditable. A small, well-logged tool using the Dataverse SDK is faster, safer and leaves a clear record of what changed.