Security Measures

AyaNova 7 (legacy version) Administration
1

Hi,

Is it possible to restrict/forbid user/s to edit or deletea workorder item/s, and its subcategories, previously entered by another user?

Thank you in advance for your help.

Angela.

2

Hi Angela
Yes you can restrict users of a security group from editing or deleting any workorder items and its subsections. Do note that this would be all workorder items and its subsections, as the restriction is for the entire feature.

For example, let’s say you want certain users to not be able to edit any fields in the Workorder Items, nor any fields in any subsection (Scheduled Users, Tasks, Labor, Parts, Misc Exp, Loans, Travel, Outside Service).

Log in as a user with full rights to Security Groups and Users such as the AyaNova Administrator
Go to the Administration navigation pane and select Users grid so that you can confirm what security group these users are a member of.
Select the Security Group to open it (let’s say it is called Techs)
Set the Security Level to Read Only for the following Internal Object’s
Object.WorkorderItem
Object.WorkorderItem.Labor
Object.WorkorderItem.Loan
Object.WorkorderItem.MiscExpense
Object.WorkorderItem.OutsideService
Object.WorkorderItem.Part
Object.WorkorderItem.Task
Object.WorkorderItem.Travel
Save the security group
Now have the users log back into AyaNova and the edited rights for the security group will now take effect
Also see the AyaNova 4 Help file section that identifies each Object in a Security Group (URL removed as for older version no longer supported - see the latest version of AyaNova)

  • Joyce
3

I was afraid of that.

It is not what we needed. We have several technicians working on the same workorder…so we wanted to avoid people changing by mistake other user’s workorder items…so if restricted the user can’t edit any items at all, including the one/s that he need to input.

Thank you for reply Joyce.

Angela.

4

Hi again Angela, sorry but that is not a feature. The way the security groups work is based on the feature as a whole, not on who entered previous data or on data itself.

  • Joyce
5

Thank you Joyce.