Guide: Setting Up Team Roles & Permissions for Your Crew
As your team grows, managing what each employee can see and do in your software becomes critical. This guide walks through setting up role-based access that protects your business and empowers your crew.
Access Control Isn’t Just a Tech Problem
When you’re a solo operator, there’s no permissions question. You control everything. But the moment you add a second person — even just an office administrator or a part-time technician — questions about access become real and consequential.
Should your field technician be able to see client payment history? Should a dispatcher be able to change invoice amounts? Should a new hire have access to your full client list and pricing on their first day?
Most small service businesses answer these questions informally at first: they hand out logins, trust people to stay in their lane, and hope for the best. This works until it doesn’t — until a pricing structure gets changed accidentally, a client record gets deleted, or a departing employee has access they shouldn’t.
Role-based permissions in Job Pilot let you answer these questions explicitly and enforce them automatically. This tutorial walks through each role, what it controls, and how to configure your team correctly.
Why Role-Based Permissions Matter
Privacy and data security. Your client list, pricing structure, and revenue numbers are sensitive business information. Not everyone on your team needs to see all of it. A technician who knows your margins and client contact details is a technician who might take that information with them if they leave.
Preventing costly mistakes. The most expensive errors in field service management are usually accidental: an invoice edited to the wrong amount, a job deleted instead of rescheduled, a client’s payment information changed incorrectly. Limiting who can take certain actions limits the blast radius of any single mistake.
Clarity for your team. When people know what they can and can’t do, they stop guessing and stop asking. A dispatcher who knows they have full scheduling access but no invoice access doesn’t need to escalate every billing question — they know it’s not their domain.
Compliance. If you ever have an audit, a dispute, or a legal matter, the ability to show who had access to what and when is valuable. Role-based access creates that audit trail.
The Five Role Types in Job Pilot
Job Pilot uses five built-in role types. Understanding what each role can and cannot do is the first step to assigning them correctly.
Admin
The Admin role has full access to everything in Job Pilot: all client records, all financial data, all settings, all reports, team management, billing configuration, and integrations. Admin can create and delete records across every module.
Who should be an Admin: The business owner and, if you have one, a trusted operations manager or office manager who needs to manage the full system. Keep the number of Admins as small as possible. You typically don’t need more than two.
Manager
Managers have broad operational access but are limited on a few sensitive areas. They can manage jobs, clients, quotes, and invoices. They can view most reports. They cannot access company billing settings, change subscription details, or manage integrations.
Who should be a Manager: A senior office staff member or a lead technician who runs jobs but doesn’t need access to the backend business settings. Managers can do most of what an Admin can do for day-to-day operations.
Dispatcher
Dispatchers have full scheduling access: they can create jobs, assign technicians, adjust schedules, and view all job details. They can view client contact information. They cannot create or edit invoices, view financial reports, or access client payment information.
Who should be a Dispatcher: An office coordinator or scheduling assistant whose primary job is managing the calendar. This is the right role when you want someone to have complete scheduling autonomy without exposing financial data.
Worker (Field Technician)
Workers see only the jobs assigned to them. They can view job details, navigate to job locations, update job status (en route, on site, complete), complete assigned forms and checklists, and add notes or photos to their jobs. They cannot see other technicians’ jobs, client financial history, or any business settings.
Who should be a Worker: Your field technicians and service crew. The Worker role is designed specifically for field use — it shows them exactly what they need and nothing they don’t.
Limited Worker
Limited Workers have the same access as Workers but with one additional restriction: they cannot see the client’s contact information (phone number, address) until they are actively checked in to a job. This is useful for new hires or contractors where you want to limit data exposure before trust is established.
Who should be a Limited Worker: New hires in their first few weeks, seasonal employees, or subcontractors. You can promote them to Worker when you’re confident they should have full client contact visibility.
How to Invite Team Members and Assign Roles
Step 1: Navigate to Team Management
In Job Pilot, go to Settings > Team and click Invite Team Member.
Step 2: Enter their information
Add the team member’s name and email address. They will receive an invitation email with a link to set up their password. You don’t set their password — they do.
Step 3: Assign their role
Select the appropriate role from the dropdown. Review the permission summary that appears below the dropdown to confirm the role gives them what they need and nothing more.
Step 4: Set their work schedule (optional)
For field technicians, you can set their default work schedule (days and hours) so they appear correctly in the scheduling view. This also controls when they appear as available in the dispatch board.
Step 5: Notify them
The invitation email includes a brief description of Job Pilot and a link to download the mobile app if they’re a Worker or Limited Worker. Consider supplementing the email with a quick walkthrough on their first day — five minutes showing them how to find their jobs, update status, and complete forms goes a long way.
Best Practices for Role Assignment
Use the principle of least privilege. Give each person the minimum access they need to do their job. It’s always easy to upgrade someone’s access. It’s harder to un-ring the bell after something goes wrong with too-broad permissions.
Default new hires to Limited Worker. Even if you eventually plan to give them full Worker access, starting with Limited Worker during their first few weeks is a simple way to limit exposure while you’re still building trust.
Be thoughtful about the Dispatcher role. Dispatchers need full scheduling access to do their job well. But the Dispatcher role does not include invoice access — by design. If your dispatcher also handles billing, consider the Manager role, which includes both.
Avoid giving Admin access to field techs. It’s tempting to give your most trusted technician Admin access so they can “handle anything.” Resist this. Admin access exposes pricing, margins, client payment data, and company financial information. The Worker role is designed to give field technicians everything they need without these exposures.
Document your role assignments. Keep a simple internal note — even a spreadsheet — logging each team member’s name, role, and the date their access was set up or changed. When you’re managing a team of ten or more people, this audit trail becomes valuable quickly.
Setting Up a Dispatcher Without Admin Access
A common question: “I want my dispatcher to handle all scheduling but I don’t want them to see our invoices or pricing. How do I do that?”
The Dispatcher role in Job Pilot is built exactly for this. Here’s what a Dispatcher can do:
- Create, edit, and delete jobs
- Assign jobs to any technician
- View and edit all job details and notes
- View client contact information and service history
- Manage the full dispatch board and calendar
- Send appointment confirmations and reminders
- View technician locations on the map
And here’s what a Dispatcher cannot do:
- Create, edit, or delete invoices
- View or change client billing/payment information
- See financial reports or revenue data
- Access company settings or integrations
- Add or remove team members
If you have a dedicated scheduling coordinator, this is almost certainly the right role for them. They get full operational autonomy over the calendar without exposure to the financial side of the business.
Managing Permissions as Your Team Grows
When your team is small, role management is simple. As you grow past five or ten employees, a few additional practices help:
Review access quarterly. Once every three months, pull up your team list and confirm that each person’s role still matches their current responsibilities. Roles drift over time — a temporary promotion becomes permanent, a part-timer’s responsibilities change — and the permissions don’t always get updated to match.
Revoke access immediately when someone leaves. This is non-negotiable. The moment an employee gives notice or is let go, revoke their Job Pilot access. Don’t wait until their last day. Former employees with active logins — even trustworthy ones — represent a security exposure. In Job Pilot, go to Settings > Team, find the team member, and click Deactivate Account.
Use deactivation, not deletion. When a team member leaves, deactivate their account rather than deleting it. Deactivation preserves their job history and activity log, which you may need for reference. It also prevents their completed jobs from showing orphaned or incomplete in your records.
Audit the Admin list periodically. If you’ve had turnover in office or management roles, it’s worth confirming that the people currently assigned as Admin are the people who should be Admins. A former manager whose role changed but whose Admin access was never downgraded is a common oversight.
A Quick Reference: Role Permissions at a Glance
| Capability | Admin | Manager | Dispatcher | Worker | Ltd. Worker |
|---|---|---|---|---|---|
| View own assigned jobs | Yes | Yes | Yes | Yes | Yes |
| View all jobs | Yes | Yes | Yes | No | No |
| Create/edit jobs | Yes | Yes | Yes | No | No |
| View client contact info | Yes | Yes | Yes | Yes | After check-in |
| Create/edit invoices | Yes | Yes | No | No | No |
| View financial reports | Yes | Yes | No | No | No |
| Manage team members | Yes | No | No | No | No |
| Access company settings | Yes | No | No | No | No |
Setting up roles correctly is one of those foundational tasks that pays invisible dividends for years. Do it right once, review it periodically, and your team can operate with confidence — knowing they have what they need and your business data is protected.