By using this website, you agree to our Terms of Use (click here)
Notifications
Clear all
Everything Else
2
Posts
2
Users
0
Reactions
2,989
Views
July 27, 2017 3:20 pm
Rather than having to alter many roles to accommodate access to the Approvals screen, would it be appropriate to create ONE Role for AP Approvals and simply add that role for anyone involved in the approval process? Trying to determine best-practices.
1 Reply
July 28, 2017 11:31 pm
Personally, I'm terrible when it comes to security, but I see it done several ways:
- By Job Role / Title. I find this difficult to do in SMB companies because roles and responsibilities change so frequently or aren't that defined to begin with.
- By Module / Screen Group / Screen. This is what you're suggesting and it seems like a pretty clean approach to me.
- By User. Works when the company culture is one of wearing multiple hats and each users seems to need a collection of random things. Then, when someone new is added, you just copy the security from an existing user role to a new user role.