When defining the inspectors roles, the segment of filing jobs gives some restrictions that is not optimal in a production perspective.
For Example a technician should not be able to file a certificate job, but they should be able to file a inspection job with the technical authority or a dedicated authorized person as responsible. So if we remove the option of filing others jobs it defines that rules for all aspects even the standard aspect where the inspectors are empowered by the companys authority.
It is strongly requested that this functionality is adjusted so that different levels of responsibility may be entered.
Hi @fjkr
Just to clearify: You are looking for more options in the “file jobs” and “file others’ jobs” setting, because inspectors and technicians have different experties that allows them to only file certain types of jobs.
I am wondering what you define as types of jobs, what those options should be if we extend that setting to include different options? You mention certificate job and inspection job as examples, but the way we differentiate those in the system is on the type of form you select. Form 3 will be a certificate job, and Inspection report will be an inspection job. I am not sure this is what you are looking for.
I recently tested restricting the access for one of my good technicians by not being “responsible” in a certificate job, His task was to make the certificate and set me as responsible, he then had access to “archive others jobs” and could as expected archive the job without my interference, specifically for certificate jobs this introduces a lack control and verification.
Then it is my understanding that if i do restrict even further that they can not archive others jobs, we loose the opportunity for mentorship, as it is my understanding that this rule would also then apply to all inspection jobs, as an example if Per is being mentored by Pål, and Pål is set as responsible, Per would not be able to archive the inspection.
Is it correct to say that the privilige “Filing other’s job” is too generic and should be broken down into mandatory inspection and certificate job? Would that solve the problem?
That would be a good step in the right direction yes, as the level of scrutiny tends to follow the possible implications of the document being produced. A mandatory inspection can be performed on inspector level, whilst certification documents usually involves roles that holds the overall responsibility.
We have landed the items list for the winter release, and one of the items is to improve the Users and Roles setting. This product idea is one to look at when working on that item.
I will get back to you with updates going forward.
