Dynamics 365 Field Service Security Roles and Project Closure
Precision measurement group
In short
How should security roles be set up in Dynamics 365 Field Service?
In Field Service, wrong access rights cost twice: dispatchers who cannot do their job, or users who can change records they should not. The client needed security roles that matched how its service team works, and a delivery that closed cleanly. We mapped three roles across 27 tables and worked the remaining tickets down to finish the project.
Results in numbers
- tables secured by role
- 27
At a glance
- Three security roles across 27 tables
- Eight rights at four access levels per table
- Open points tracked to project closure
The client
The client is a group of precision measurement businesses with operations worldwide. This work covered its Dynamics 365 Field Service delivery, where service teams plan work orders and book technicians.
What it was costing them
- Over-broad access: standard Field Service roles can give users more rights than their job needs.
- Dispatch friction: a role that is too narrow stops dispatchers creating work orders or booking resources.
- Reference data control: products, price lists, agreements and assets need clear rules on who may change them.
- Delivery risk: open tickets at the end of a project delay acceptance and sign-off.
What we did
We built the Field Service security roles in a table-by-table matrix, agreed the open points and worked the remaining delivery tickets down to closure.
- Clear roles for clear jobs: Field Service Administrator, Dispatcher and Inventory Purchase, each on its own sheet.
- Every table decided: 27 tables, from work orders and bookings to agreements, assets and price lists, each rated for create, read, write, delete, append, append to, assign and share.
- Access sized to the organisation: each right is set at user, business unit, parent and child business unit or organisation level.
- Admins stay in control: the administrator role has organisation-level rights on all 27 tables.
- Dispatchers can dispatch: organisation-level create, read and write on resources, bookings and work orders, with assign and share inside the business unit family.
- Purchasing kept narrow: the inventory purchase role covers products and complaint records only.
- Open points visible: items to check, such as append, assign and share on accounts, sit beside the rights.
- A clean finish: remaining delivery tickets were worked down to closure by the end of July 2023.
Results
- Three security roles documented across 27 tables, with eight rights and four access levels for each table.
- Open points on account append, assign and share, and on dispatchers assigning incident types to work orders, recorded for review.
- Closure phase in July 2023, with about 35 hours of work to finish the whole project by the end of the month.
The risk most teams miss
Security roles drift. By month three a Field Service update adds a table or a new team joins, and someone copies the administrator role as a quick fix. We kept the rights in one matrix with a legend, so each change can be reviewed, and marked open points instead of leaving them implicit. We test each role with a real user before every release.
What we would add today
Improvements we would add on top of what is live.
- Move the roles into a managed solution deployed by Power Platform pipelines, so every environment has the same roles.
- Use Dataverse column security profiles on price and cost fields instead of widening table rights.
- Assign roles through Entra ID group teams, so joiners and leavers change access without a ticket.
- Add Managed Environments and turn on Dataverse auditing for role changes.
- Report on work orders and first-time fix in Power BI or Fabric, with row security on the same business units.
Technology
Dynamics 365 Field Service, Dataverse security roles and business units, Excel role matrix, SharePoint document management, Microsoft Entra ID.
Tell us which Field Service roles your team shares today, and we will tell you which rights each person actually needs.
Products and capabilities
- Dynamics 365
- Dynamics 365 Field Service
- Dataverse
- security roles
- business units
- access control
The service behind this work
Dynamics 365The service behind this work
Power Platform governanceMore on this industry
Manufacturing and distribution
Related use cases
Operations and field workDesktop Automation That Opens Email Links on a Virtual Machine
When a team must read an email, find the link inside and open it every time, the work is small but never stops, and it depends on whoever remembers. The client wanted this automated on a machine with only one generic account. We built a desktop flow on a virtual machine that does the whole sequence.
Route and Crew Assignment Optimiser for On-Site Workers
Planners at a multi-site materials business often assign people and vehicles to jobs by phone and spreadsheet. A crew sent without the material, or on a long route when a closer team was free, costs fuel, hours and customer patience. We built an app that suggests assignments by distance, availability and stock.
Multi-Level Automated Approval Chains with Power Automate
Getting one approval can take a string of reminder emails, and nobody can say where a request is stuck. We built one reusable Power Automate approval flow that asks each approver in turn and records every answer.
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.