Boaz Schonherz Hi, Boaz. I can second this request. The permissions need to be more in depth and not grouped together.

For example, "Other Users Jobs - Can view everyone's jobs, schedule, and messages." I feel that a tech should only be able to view what is assigned to him, not everyone. Now, I know that we can turn this on, but it blocks that tech from viewing previous job/visits.

There should be a way that "Tech A" should not see where "Tech B" is going to be today. However, if "Tech A" is scheduled for a project that "Tech B" was at last month, "Tech A" should be able to view that previous visit from "Tech B."

Now with this being said, I can add to Paula Uribe's comment of -

"For techs to view but not to edit any information inside the jobs. They should be able to see it but not change anything of it."

With what I mentioned above, if "Tech A" is on this project/job today, "Tech B" should be able to see job items, estimates, etc. but they should not be able to edit/change anything that "Tech A" did, unless both are actually assigned to that ticket/job number.

I hope this makes sense. If you have any questions just let me know.

Thank you!

Thank you for the detailed feedback and for taking the time to explain your use cases.

As we do offer several permissions today to control what technicians can access and modify, it's clear that there’s room for improvement in handling more scenarios, like restricting visibility across users while still allowing access to relevant historical data, or enabling view-only access to job details.

We’ll continue gathering feedback in this area and use it to guide future improvements to our permissions.

Thanks again for sharing this, please keep the ideas coming!

Boaz / Product