Getting your team set up correctly from the beginning will save you significant time down the road. In my experience working with organizations rolling out FieldPulse, the invitation and role assignment process is where a lot of teams either build a solid foundation or create ongoing administrative headaches. What I typically recommend is taking a few minutes to think through your organizational structure before you start clicking through the interface.
Understanding the Role Hierarchy
Before you send any invitations, it is worth understanding how FieldPulse structures access. There are four primary role levels:
- Account Owner — Full access to all settings, billing, and user management. Only one per account.
- Administrator — Can manage users, configure workflows, and access all operational data. Cannot delete the account or change billing.
- Dispatcher — Can create and assign work orders, view schedules, and communicate with technicians. No access to user management or account settings.
- Technician — Mobile-focused access. Can update assigned work orders, capture photos and signatures, and complete checklists. Cannot see other technicians' schedules or unassigned jobs unless explicitly granted.
In my experience, the distinction between Administrator and Dispatcher is where most organizations need to spend some time thinking. If someone needs to adjust technician availability or configure notification rules, they need Administrator access. If they only need to schedule and reschedule jobs, Dispatcher is appropriate.
Sending Invitations
To invite a new team member:
- Navigate to Settings → Team Management.
- Click the Invite User button in the upper right.
- Enter the email address and select the appropriate role.
- Optionally add a personal message to the invitation email.
- Click Send Invitation.
The invited user will receive an email with a link to create their account. Invitations expire after 7 days. What I typically recommend is following up directly if someone has not accepted within a day or two — email filters often catch these messages.
Configuring Permissions Beyond the Base Role
Each role has default permissions, but Administrators can adjust certain capabilities:
- Technicians can be granted permission to view the full dispatch board, create new customers, or see pricing information.
- Dispatchers can be restricted from viewing financial reports or customer billing details.
- All users can have access limited to specific service areas or job types.
To modify these, select a user from the Team Management list and click Edit Permissions. Changes take effect immediately without requiring the user to log out.
Best Practices from Implementation
From what I have seen work well in practice:
- Start with fewer Administrators than you think you need. You can always promote someone later.
- Technicians who also do light dispatching can be given Dispatcher access rather than trying to stretch the Technician role permissions.
- Document your permission structure somewhere — six months from now you will not remember why certain users have custom settings.
If you are migrating from another system and have a large team to onboard, you may want to review the Migrating from Legacy Field Service Software guide, which covers bulk invitation strategies.
Troubleshooting Common Issues
Invitation not received: Check spam folders first. The invitation comes from noreply@fieldpulse.com. You can resend from the Team Management screen by clicking the three-dot menu next to the pending user.
User created account but cannot see jobs: Verify they were assigned the Technician role and that jobs are actually assigned to them. Technicians do not see unassigned work orders by default.
Need to change someone's role: Administrators can edit roles at any time. Account Owners cannot be demoted — you must transfer ownership first.
For more detail on the permission system and security considerations, see Managing User Roles and Permissions.
