How to Set Up a Read-Only Dispatcher Console in Salesforce Field Service
In this Office Hours Insight session, Leigh-Anne Nugent walks through a practical Salesforce Field Service challenge: how to give users visibility into the dispatcher console without letting them drag, drop, or make scheduling changes. This is a useful session for teams that need read-only access for supervisors, support roles, or anyone who should see the board without changing it.
LESSONS YOU CAN TAKE FROM THIS:
1. Read-only access is possible, but it takes deliberate setup
This is not a simple toggle you switch on and forget. Leigh-Anne shows that creating a read-only dispatcher console requires a combination of permission sets, a permission set group, and a muting permission set to remove the dispatcher actions you do not want users to have.
2. Profiles can quietly override your plan
One of the biggest troubleshooting moments in this session is discovering that the unwanted access was not coming from the permission set group at all. It was coming from the user’s profile. That is a strong reminder that when security behaves unexpectedly, you need to check user access summaries carefully and confirm exactly where the custom permissions are being granted.
3. Muting permissions is only part of the story
The muting permission set is helpful, but it only works once the underlying access model is clean. If the profile still grants dispatcher console permissions, muting alone will not create the locked-down experience you want. This session shows why permission set strategy and profile cleanup need to work together.
4. The end result is a cleaner operational model
Once configured correctly, the user can still see the dispatcher console, view the key list views, and understand the schedule, but they cannot drag and drop appointments or use the normal console actions. That makes this a strong pattern for organizations that want broader visibility without risking accidental scheduling changes.
KEY TAKEAWAYS:
A read-only dispatcher console can be built with permission sets, permission set groups, and muting permissions.
User access summaries are essential when troubleshooting unexpected access.
Profiles may still be granting dispatcher console permissions behind the scenes.
Removing drag-and-drop and action access creates a safer visibility-only experience.
This setup is useful for supervisors, observers, and operational stakeholders who need insight without edit access.
