By Heather Lawson, field-service access administrator with 9 years of experience configuring technician roles, dispatch teams, and operational reporting
Last reviewed: July 21, 2026
FieldPulse separates individual users from teams, allowing a business to group employees for scheduling, assignments, and operational work. A missing job, customer field, project, or report may be caused by the employee’s role, team membership, saved filters, or seat type rather than deleted data.
This independent guide is not operated by or affiliated with FieldPulse.
Check the original user first. Skip creating a replacement employee account until the person’s role, team, permissions, filters, and login method have been reviewed.
What is FieldPulse?
FieldPulse is field service management software for scheduling, dispatching, customer records, jobs, estimates, invoices, payments, reporting, and mobile technician work. Its platform can be adapted through custom workflows, teams, permissions, saved views, and configurable fields as a service business grows.
The account structure can include:
- Individual users
- Teams
- Team Managers
- Administrators
- Service Agents
- Full-access seats
- Field-only seats
- User-specific settings
- Role-controlled fields
Those controls solve different problems.
A team groups people for work. A role determines what a person can manage or view. A seat affects the level of platform access purchased for that user. A saved filter changes which records are currently shown.
Treating those controls as one setting leads to the wrong fix.
User or team?
FieldPulse defines a user as an individual who can access the platform. A team is a group of users who work together on particular tasks or projects. A business can operate as one team or divide employees into several teams based on its needs.
Every FieldPulse account must have at least one team. A Default Team is included automatically and can be renamed or changed. Additional teams are created under Company Settings, User Accounts, and the Teams tab.
This matters during setup.
A company may create:
- North Service Team
- South Service Team
- Install Crew
- Maintenance Team
- Commercial Dispatch
- Emergency On-Call
Those names are operational choices, not FieldPulse requirements.
Use teams when employees genuinely share scheduling, assignment, or management needs. Skip creating one team for every temporary project unless the extra structure improves daily work.
Too many teams can make filters, dispatch views, and reporting harder to interpret.
Who can manage a team?
When a team is created, the administrator enters its name, optional description, managers, and members. FieldPulse says only Administrators and Team Managers can serve as team managers, while any supported role can be added as a team member.
That rule explains a common setup problem.
An administrator tries to make a Service Agent the manager of an installation crew but cannot select that person as the team manager. The user may be a valid member, yet the assigned role does not permit team management.
Check the role first.
Do not upgrade every lead technician to Administrator merely to let that person coordinate a small team. Review whether the Team Manager role supplies the needed access without opening broader company settings.
Access should match the work.
Full-access and field-only seats
FieldPulse uses seat-based pricing. Full-access seats cover the broader platform, including scheduling, dispatching, customer management, estimates, invoices, Pricebook, and reporting. Field-only seats are intended for mobile workers who need assigned jobs, job details, notes, file uploads, and clock-in or clock-out functions without full back-office access.
A missing menu may therefore be expected.
A field technician may sign in successfully and see assigned work but no reporting dashboard, company settings, or accounting controls. That does not automatically indicate a broken app.
Check the seat and role first. Skip reinstalling the mobile application because an office feature is absent.
The useful questions are:
| Access question | Possible explanation |
|---|---|
| Can the user log in? | Account and authentication issue |
| Can the user see assigned jobs? | Team, assignment, filter, or sync issue |
| Can the user open office tools? | Seat or role limitation |
| Can the user manage other employees? | Manager or administrator permission |
| Can the user see financial data? | Role and record permissions |
The company should decide what each position needs before buying or assigning seats.
Why a technician cannot see a job
A job can be present in FieldPulse but absent from one technician’s screen.
Possible reasons include:
- Another user or team is assigned.
- The job is unscheduled.
- The job is unassigned.
- The selected date range excludes it.
- A status filter hides it.
- The technician has limited access.
- The mobile device has not synchronized.
FieldPulse’s schedule filters can show categories including Unscheduled, Unassigned, Unscheduled & Unassigned, and Open Jobs, along with job-status fields.
Start with the main Jobs or Schedule view and clear the filters.
Skip creating another job because it is missing from a technician’s personal schedule. A duplicate can produce two work orders, two customer notices, or conflicting invoices.
Then confirm the assigned user and team.
One practical mistake occurs when dispatch assigns a team but expects one particular technician’s personal view to update. The person still needs to be included in the relevant assignment structure and have access to the record.
Saved filters can hide valid work
FieldPulse expanded job and project filtering in March 2026. Users can save custom filters as tabs for quick access. Project filters include defaults such as Open, Closed, and Unassigned, plus options for project status, active or archived records, customer name, and assigned teams.
Saved views are useful. They also retain old assumptions.
A tab called “Today’s Installations” may still contain a team or status filter created months earlier. New installation jobs assigned to another crew will not appear, even though the tab’s name sounds comprehensive.
Review the active filter set first.
Do not treat a saved-view title as proof of what the view includes. Open the filter panel and inspect every condition.
This is a hands-on support rule: broad search before record recreation.
Schedule Map team filters
FieldPulse’s Schedule Map supports filtering by teams, job status, and job queue. It can also display unscheduled and unassigned jobs in the Day view and show jobs using status colors or team-member colors.
A dispatcher comparing maps with another employee may see a different set of jobs because their filters or visual settings differ.
Check:
- Date
- Team filter
- Status filter
- Job queue
- Unscheduled and unassigned display
- Color mode
Do not move a job merely because its pin is absent from one filtered map.
The map is a view of selected records. It is not the source of the assignment itself.
For availability, FieldPulse also documents a Team Dispatch View that can be used to find openings among team members. Selecting a start time defaults to a one-hour duration in that documented workflow, so the dispatcher should change the duration when the actual job requires longer.
One hour is a starting value, not a universal service duration.
Custom fields can be hidden by role
FieldPulse customer custom fields can be configured with visibility permissions by role. An administrator can decide whether Service Agents, Team Managers, or other applicable users should see a field.
That creates a specific mismatch.
The office sees a gate code, warranty classification, referral category, or commercial account note. The technician opens the same customer and cannot find it.
The field may be role-restricted.
Check Company Settings, Customers, and Custom Fields, then review Field Visibility by Role.
Skip creating another custom field called “Gate Code Mobile” until the visibility setting has been checked.
Duplicate fields fragment the customer record and make reporting harder.
FieldPulse also says newly created custom fields may require a full mobile resynchronization, sometimes including logging out and back in, before they appear in the mobile application.
Permissions first. Synchronization second.
Customer-visible fields need separate review
A customer custom field can also be marked Is Visible to Customer & Supplier. When enabled, FieldPulse says the information may appear on purchase-order PDFs, job reports, estimates, invoices, and asset reports.
This is not merely an employee-access setting.
A field such as “Customer type” may be harmless on an internal profile but inappropriate on an invoice. An internal risk note should not be exposed through a customer-facing document.
Review both controls:
- Which employee roles can see the field?
- Can customers or suppliers see it?
Do this before importing or mass-populating sensitive operational notes.
Skip assuming that “custom” means private.
Notes have their own visibility
FieldPulse Notes can be visible to the author only, managers only, or the entire business. After saving the note, the user can select Notify and choose recipients by role or individual user.
A note’s visibility and its notification list are separate.
A manager-only note can exist without notifying every manager. A company-wide note can be saved without sending an alert. An employee may therefore have access to a note but never receive a notification about it.
Check both.
Do not repost the same note in several locations merely because someone missed the alert. That produces competing versions.
A clear note should identify the related customer, job, decision, and owner. Notifications should be sent only to people who need to act.
Deactivating a user does not erase history
FieldPulse’s current help documentation says records created or edited by a deactivated user remain viewable. The former user can no longer be assigned to future work while deactivated, but historical records are preserved.
That distinction is important when an employee leaves.
Do not create replacement copies of old jobs, notes, or invoices to preserve the former employee’s history. The records remain attached to the business account.
Before deactivation:
- Reassign future jobs.
- Review team membership.
- Transfer open follow-ups.
- Check unresolved estimates or invoices.
- Review phone or notification routing.
- Preserve the correct historical user identity.
After deactivation, search the original records when reviewing past work.
The user is inactive. The history is not.
Default calendar settings can differ by user
FieldPulse allows the schedule to begin on Sunday, Monday, or its Classic view. The control is located under the user’s profile icon, My Settings, and Default Starting Calendar Date.
This is a user preference rather than necessarily one company-wide calendar.
Two dispatchers may describe “this week” differently on screen because one view begins Sunday and the other begins Monday.
Check the date headers before concluding that a Monday job moved into the wrong week.
Skip changing the actual job date to correct a display preference.
Small setting. Expensive mistake.
Teams are not customer locations
A team organizes employees. A customer location identifies where work is performed.
FieldPulse supports importing multiple customer locations and contacts, and its customer profiles can store jobs, invoices, comments, photos, files, and other history.
Do not create one employee team for every customer site merely to separate work.
Use:
- Customer locations for service addresses
- Teams for employee organization
- Tags or custom fields for segmentation
- Job assignments for specific work
- Saved filters for operational views
A commercial customer may have twenty buildings and one dedicated service team. Those are different relationships.
Keep them separate so reporting and scheduling remain understandable.
Pricing and support
FieldPulse pricing is customized according to team size, setup, and required seat access. The official pricing page says businesses purchase a set number of seats for the contract term and can add seats as the team grows.
A useful quote request should distinguish:
- Full-access administrators
- Dispatchers and managers
- Field-only technicians
- Temporary or seasonal users
- Reporting users
- Required add-ons
- Expected team growth
FieldPulse’s Help Center publishes support@fieldpulse.com and 469-382-5668 in its team documentation.
Before reporting an access problem, note the employee, role, seat type, team, affected record, active filters, web or mobile environment, and whether another user can see the same item.
Do not include credentials or authentication codes.
Frequently asked questions
What is a FieldPulse team?
A group of users assigned to work together.
Does every account have a team?
Yes. FieldPulse includes a Default Team that can be renamed or modified.
Can a Service Agent manage a team?
FieldPulse says only Administrators and Team Managers can be team managers.
Why can one user see a field that another cannot?
The custom field may have role-based visibility settings, or the mobile device may need a full synchronization.
Why is a job missing from the schedule?
Check assignments, team membership, dates, status, unscheduled and unassigned queues, saved filters, permissions, and mobile sync before creating another job.
Does deactivating a user delete their work?
No. FieldPulse says historical records remain viewable.
Are field-only seats the same as full-access seats?
No. Field-only seats provide narrower mobile access, while full-access seats include broader office and reporting functions.
What should be checked before creating another user?
Confirm the existing user’s email, login method, role, seat, team membership, assignments, permissions, and deactivation status.
