Currently there is an option in the Field App to see your tasks and everyone's tasks (when updating statuses). Would it be possible to have access levels or permissions to regulate what tasks users can see/edit apart from just assigning specific tasks?
Hello Philip,
I know we are trying to schedule a call however I wanted to give you some feedback concerning this Idea from our lead developer for Field.
If we were to implement this feature, it would need to be driven by 4D, and would require object-level permissions (i.e. Tasks) as, currently, 4D (and subsequently, Field) only has project level permissions. As this is the case, I will discuss this with the 4D product manager and seek some more feedback.
Concerning Field, for our upcoming release, 3.4.40 (due at the end of May), we will be including Task search, meaning that a user could search for a Task by using keywords (or use Task assignments). Another option would be to explore whether we can include additional filters in Field that would allow a user to find Tasks more quickly.
Kind regards,
Luke
Hi Philip,
Thanks for coming back to me so quickly and for the detailed response, it is very helpful.
Let me discuss this internally and then come back to you.
All the best,
Luke
Luke,
Thank you for your response! Currently, it seems that users can access the tasks that are assigned to them and make status changes on those tasks. A user can also view everyone's tasks, but they don't necessarily have the ability to modify everyone's statuses. Let's say you have an earthwork subcontractor who is performing mass excavation and underground utilities. You also have an electrician who is placing coduit and or underground electrical vaults. Those two groups need to be closely coordinated. I think it would be beneficial for those two groups to be able to see one anothers tasks, but they don't necessarily need to see a drywaller's tasks, let's say. I imagine that being managed through Synchro Control on the website, and the admin would have the ability to assign permissions to individual users based on certain resource properties or information embedded in the model objects. I know nothing is as simple as it initially sounds, but I think it could work.
Thanks again!
Hello Philip,
Many thanks for raising this Idea.
I have set it to "Future Consideration" as I can see the benefit of being able restrict Task visibility by role permission.
How would you see the permissions working in this scenario? Would it be, as examples, by Discipline/Craft or by project Area/Location?
Thanks in advance,
Luke