• State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 2 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

    From a governance perspective, it is worth noting that the "view all, edit subset" permission model introduces audit complexity that FieldPulse's current role architecture does not natively support.

    In my implementation, we addressed this through a structural rather than permissions-based approach:

    1. We created distinct FieldPulse accounts for each region (North, Central, South)
    2. Established a master scheduling view through the API, aggregating data for coordination purposes
    3. Regional dispatchers maintain edit rights within their account scope

    This configuration provides clean audit boundaries and satisfies our compliance requirements for data segregation. It is worth noting that this approach requires API development effort and is not suitable for all organizations.

    It is also worth noting that the Professional Services custom role mentioned above may not provide the audit logging granularity required for certain regulatory frameworks. I recommend requesting a detailed permissions matrix before proceeding with that option.

Reply
  • 0

    From a governance perspective, it is worth noting that the "view all, edit subset" permission model introduces audit complexity that FieldPulse's current role architecture does not natively support.

    In my implementation, we addressed this through a structural rather than permissions-based approach:

    1. We created distinct FieldPulse accounts for each region (North, Central, South)
    2. Established a master scheduling view through the API, aggregating data for coordination purposes
    3. Regional dispatchers maintain edit rights within their account scope

    This configuration provides clean audit boundaries and satisfies our compliance requirements for data segregation. It is worth noting that this approach requires API development effort and is not suitable for all organizations.

    It is also worth noting that the Professional Services custom role mentioned above may not provide the audit logging granularity required for certain regulatory frameworks. I recommend requesting a detailed permissions matrix before proceeding with that option.

Children
No Data