Allow access to each function within the setup menu. At the moment anyone who has access to setup maintenance can change anything.
by: Beryl v. | over a year ago | General Enhancements
Comments
I think this is too granular just on its own. You'd need "permission profiles" so that different setup functions can be delegated to different groups of people. That would make the program useable by both small/flat organisations and large/prismic organisations.
With permission profiles, you'd also be able to define functions which require dual authorisation. This would improve the security of the set up considerably.
Recommend that the security be changed to look like more like a tree structure where each icon and subselections would have a tickbox. Example (Sage MIP Non-Profit software)
Agreed - security is very poor. In some systems I have used each user has a pin number as well as a password. Each transaction eg invoice, or batch in the case of AP, before completion requires that pin to be entered to complete the transaction.
Agree with Lori E. Need a tree structure environment that mirrors the Sage 300 menu.
Needs a tree structure similar to Active Directory. Create security groups (not like the groups are done now) that you add the users to, then you assign the permissions to the groups. Have the permissions more granular so that it is easy to see what is assigned to who. Allow for embedded security groups so in certain departments, your outer groups have the basic permissions and the managers be in the embedded groups that have more permissions assigned.
Correct or create better granularity, for example in I/C BOM is under Setup Maintenance, and not Item Maintenance...
Also, it confused my low level users when they don't have access to say AR, but some of the AR functions still appear on their profile. I also agree with Lori E.
Comments
I think this is too granular just on its own. You'd need "permission profiles" so that different setup functions can be delegated to different groups of people. That would make the program useable by both small/flat organisations and large/prismic organisations.
With permission profiles, you'd also be able to define functions which require dual authorisation. This would improve the security of the set up considerably.
Recommend that the security be changed to look like more like a tree structure where each icon and subselections would have a tickbox. Example (Sage MIP Non-Profit software)
Agreed - security is very poor. In some systems I have used each user has a pin number as well as a password. Each transaction eg invoice, or batch in the case of AP, before completion requires that pin to be entered to complete the transaction.
Agree with Lori E. Need a tree structure environment that mirrors the Sage 300 menu.
Needs a tree structure similar to Active Directory. Create security groups (not like the groups are done now) that you add the users to, then you assign the permissions to the groups. Have the permissions more granular so that it is easy to see what is assigned to who. Allow for embedded security groups so in certain departments, your outer groups have the basic permissions and the managers be in the embedded groups that have more permissions assigned.
Correct or create better granularity, for example in I/C BOM is under Setup Maintenance, and not Item Maintenance...
Also, it confused my low level users when they don't have access to say AR, but some of the AR functions still appear on their profile.
I also agree with Lori E.