• State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 0 views
  • Users 0 members are here
Options
Related

Dispatcher view all technicians but only edit own team?

Anita Sharma

I am configuring FieldPulse for a multi-region operations structure and require clarification on the granularity of role-based access control.

Configuration details:

  1. We have 3 regional dispatch teams (North, Central, South)
  2. Each team has 2 dispatchers
  3. Dispatchers must coordinate scheduling across regions for resource sharing
  4. Dispatchers should not modify technician assignments outside their assigned region

I have reviewed the Admin, Manager, and Dispatcher role definitions in the documentation. The Manager role permits editing of all technicians, which exceeds our requirements. The Dispatcher role does not appear to support hierarchical scoping by team or region.

Please confirm whether the following configuration is achievable:

  • View permission: All technicians (read-only visibility across organization)
  • Edit permission: Technicians assigned to the dispatcher's specific team or region only

I have confirmed that the Team field is populated for all technician records. I am operating on FieldPulse version 3.2.1.

Is this achievable through native configuration, or does it require a custom role configuration that must be escalated to FieldPulse support?

Parents
  • 0

    In my experience working with multi-region dispatch configurations, the Professional Services scoped role is the path that aligns with your compliance requirements. What I typically recommend is preparing the following documentation before your scoping call:

    1. A matrix of roles (Dispatcher North, Dispatcher Central, Dispatcher South) mapped to Team values
    2. Specific actions that must be permitted versus prohibited (e.g., can they view but not reassign? view schedule only?)
    3. Your audit retention requirements

    The custom role configuration uses a backend permissions framework that is not exposed in the standard UI. In my experience, the implementation timeline is 5-7 business days following the scoping call, assuming the permission matrix is straightforward.

    It is worth noting that this configuration will place your organization on a non-standard permissions path, which means future feature releases may require additional validation. I typically recommend that customers on custom roles maintain a test environment or schedule a validation window following each quarterly release.

    I will note that the cost for this configuration is typically absorbed into an existing Professional Services engagement if you have active hours, or it can be scoped as a standalone micro-engagement.

  • 0 in reply to Daniel Cho (Staff)

    Anita, I'm connecting you directly with Daniel's team. You should receive a calendar invite within the hour for a 30-minute scoping call.

    As a heads up — the scoped role will require you to maintain the Team-to-user mapping in a specific format that Daniel's team will document. It's straightforward once set up, but worth planning for in your user provisioning process.

    Let me know if you need any other context before the call!

Reply Children
No Data