Why Your Salesforce Field Service Technician Can’t Log In, and How to Fix It
In this Office Hours Insight session, Leigh-Anne Nugent walks through a real-time troubleshooting scenario inside Salesforce Field Service Mobile. From permission set groups to app access and list view setup, this episode shows how small configuration gaps can block technician login, and why methodical testing matters when rolling out mobile tools.
LESSONS YOU CAN TAKE FROM THIS:
1. Login issues usually point back to setup
When a technician cannot get into the mobile app, the problem is often not the app itself. It is usually tied to permissions, license assignments, or missing access settings that need to be validated step by step.
2. Permission set groups still need a second look
Even when setup is generated through the new setup menu, it is smart to confirm exactly which permission sets were included. A group may look complete on the surface, but one missing permission can stop the entire mobile experience from working properly.
3. Solving one issue often reveals the next one
Getting past login is only the first checkpoint. Once access is restored, the next layer is making sure the technician can actually see the right records, views, and appointments inside the app. That is where deeper usability testing starts.
4. Real implementation requires hands-on validation
This session is a good reminder that configuration is not just about enabling features. It is about testing as the actual end user, spotting friction early, and making small fixes before they turn into bigger rollout problems.
KEY TAKEAWAYS:
Mobile login issues often come from missing permissions or incomplete setup.
Permission set groups should always be reviewed, not just assumed correct.
Technician access needs both login permissions and proper app visibility.
Default views and assigned records affect what users can do after login.
Testing from the technician’s perspective is essential for a clean rollout.
