We have a number of billing groups, with monies deposited from those groups
going into different credit card merchant accounts. When I batch a group of
credit cards, it bunches all the billing groups together (as it should.)
My solution was to create an operator group that ONLY had access to ONE
billing group. That way, only those credit cards that I wanted to batch for
that group would actually be affected. To date, I have been unable to make
this work. It's as if the security options I am setting up are not being
used at all.
Is this a problem with Emerald, our SQL server, or what? Anyone have any
----- Original Message -----
From: "Eric" <firstname.lastname@example.org>
Sent: Wednesday, December 08, 1999 5:38 PM
Subject: [Emerald] Security Configurations and Privileges
> We have enabled security on Emerald, and almost everything works the way
> We have limited access for this group to only "Services" and "Incidents".
> We do not want them to be able to add any MBR's and have therefore removed
> rights to the MBR privileges. We have also tried adding just "Read"
> privilege to MBR for this group, but same resaults.
> When we login as an operator of this group, we are still able to Add or
> Modify any MBR in their "Billing Group".
> Has anyone run across this or know of something we are probably missing?
> Thanks for the help!
> Eric Jensen
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: