Forum Discussion

SerenG's avatar
SerenG
Contributor 2
18 days ago
Solved

How To Customize Jobber Checklists and User Permissions?

Hi all,

We are implementing Checklists for each job to ensure all tasks are attended by team, if there's anything further to be reported or if they completed all safety steps etc. These checklists are intended for internal records only and are not meant to be shared with clients.

However, we just realised that employees need further access to see all jobs and reports in Jobber) and they can send these Checklists to the clients.

The crew can use the Share/Email option to send completed forms directly to clients. We'd like to disable this feature based on user roles or permissions, so that only designated administrative staff can share forms externally.

Having a permission such as "Allow users to share/email Job Checklist" or not giving any permission to access all jobs and reports in Jobber would help prevent accidental distribution of internal documents while still allowing crew to complete the checklists in the field.

  • Hey there! You’ve hit on a very common pain point. It’s incredibly frustrating when you want to use checklists for internal quality control, but the app layout makes it a bit too easy for a tech to accidentally blast them to a client.

    ​As Jobber stands right now, there isn’t a granular, standalone toggle to disable the "Share/Email" option specifically for checklists. If a technician can view and complete a visit, they have the ability to send it.

    ​Until Jobber adds that specific permission, here are the best workarounds to protect your internal records:

    • Tighten Global Permissions: If your crew has broad access just to navigate the system, drop them down to "Show Allowed Actions Only" and "View their own schedule." This doesn't remove the email button on their jobs, but it completely locks them out of company-wide reports, financial data, and other unassigned work.
    • Establish a "Save Only" Protocol: Train your team to treat the checklist as a static form. They should fill it out, hit Save, and close the visit. Make it a strict company policy that the "Share" menu belongs entirely to the office admin team.
    • Move Sensitive Data to Internal Notes: If your checklists contain internal flags or property damage notes that absolutely cannot be seen by clients, consider moving those specific questions into Internal Job Notes. Note visibility can be locked down much tighter in your team settings.

    Pro Tip: Definitely post this exact scenario in the Product Feedback section here on the community. Jobber's product team watches user-permission requests closely, especially when it comes to preventing accidental client communication.

     

    ​Hope this helps you build some guardrails for now!

1 Reply

  • Hey there! You’ve hit on a very common pain point. It’s incredibly frustrating when you want to use checklists for internal quality control, but the app layout makes it a bit too easy for a tech to accidentally blast them to a client.

    ​As Jobber stands right now, there isn’t a granular, standalone toggle to disable the "Share/Email" option specifically for checklists. If a technician can view and complete a visit, they have the ability to send it.

    ​Until Jobber adds that specific permission, here are the best workarounds to protect your internal records:

    • Tighten Global Permissions: If your crew has broad access just to navigate the system, drop them down to "Show Allowed Actions Only" and "View their own schedule." This doesn't remove the email button on their jobs, but it completely locks them out of company-wide reports, financial data, and other unassigned work.
    • Establish a "Save Only" Protocol: Train your team to treat the checklist as a static form. They should fill it out, hit Save, and close the visit. Make it a strict company policy that the "Share" menu belongs entirely to the office admin team.
    • Move Sensitive Data to Internal Notes: If your checklists contain internal flags or property damage notes that absolutely cannot be seen by clients, consider moving those specific questions into Internal Job Notes. Note visibility can be locked down much tighter in your team settings.

    Pro Tip: Definitely post this exact scenario in the Product Feedback section here on the community. Jobber's product team watches user-permission requests closely, especially when it comes to preventing accidental client communication.

     

    ​Hope this helps you build some guardrails for now!