Although, from an internal control standpoint, there could be some use for disallowing. For example, you may want anyone who is allowed to create a purchase order to be disallowed from receiving and vice-versa. So, if you make the mistake of assigning an individual to both the purchasing and receiving group, he could not do either job. You will find out about these sort of problems as soon as there is a need to rectify them. The way to correct that problem is to remove the individual from one of the groups. This sort of thing depends on how strong you want your internal controls, and whether or not you want Vantage to be the internal control enforcer. Obviously, as Ken has noticed, and you have made clear, using too much disallowing will cause more problems than it solves.
Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Manasa Reddy
Sent: Friday, June 06, 2008 1:54 PM
To: vantage@yahoogroups.com
Subject: {Disarmed} RE: [Vantage] Menu security best practices?
My only suggestion is to not bother with "disallowing". Give allow
access by moving groups to the right-side. If the group is not on the
right-side then they are disallowed automatically....much easier to deal
with!
M. Manasa Reddy
manasa@...<mailto:manasa%40weldcoa.com>
P: 630-806-2000
F: 630-806-2001
________________________________
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
Of Ken Long
Sent: Friday, June 06, 2008 3:49 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Menu security best practices?
We're going live on 8.03 in a few weeks and I'm setting up menu
security. All access permissions are done by group, not individual
user. However, I started adding users to multiple groups to give them
access to multiple menu items and I ran into a snag. Seems that the
user account accumalates the "disallows" and ends up with less access
than they need.
I'm thinking that I can overcome this problem by creating a new group
for that user and assigning the necessary menu access to the new
group. Does this sound reasonable or is there a better, faster,
cheaper way?
Thanks,
Ken Long
Lectrosonics, Inc.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Manasa Reddy
Sent: Friday, June 06, 2008 1:54 PM
To: vantage@yahoogroups.com
Subject: {Disarmed} RE: [Vantage] Menu security best practices?
My only suggestion is to not bother with "disallowing". Give allow
access by moving groups to the right-side. If the group is not on the
right-side then they are disallowed automatically....much easier to deal
with!
M. Manasa Reddy
manasa@...<mailto:manasa%40weldcoa.com>
P: 630-806-2000
F: 630-806-2001
________________________________
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
Of Ken Long
Sent: Friday, June 06, 2008 3:49 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Menu security best practices?
We're going live on 8.03 in a few weeks and I'm setting up menu
security. All access permissions are done by group, not individual
user. However, I started adding users to multiple groups to give them
access to multiple menu items and I ran into a snag. Seems that the
user account accumalates the "disallows" and ends up with less access
than they need.
I'm thinking that I can overcome this problem by creating a new group
for that user and assigning the necessary menu access to the new
group. Does this sound reasonable or is there a better, faster,
cheaper way?
Thanks,
Ken Long
Lectrosonics, Inc.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]