Re: [Emerald] Security Configurations and Privileges

Eric ( )
Thu, 09 Dec 1999 13:12:56 -0500

What about the issue of limiting access to MBR's and the group can still
access, create, delete, etc. (please see my previous post)
Also, is there something we have to give the op group access to, so that
they can click "none" on the "Setup Charge" when creating a new sub
account? Right now, the way we have it set, when the op group creates a sub
account, the setup charge is not listed, and if they click save, an error
pops up "Pro-rate failure: The query and the views in it exceed the limit
of 16 tables", and there is a charge of $0 added to their account.

Thanks for the help.
Eric Jensen

At 09:52 AM 12/9/99 -0800, you wrote:
>Chris Melching wrote:
> >
> > I'm having a similar problem. What I am trying to do is this:
> >
> > 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
> > ideas?
>2.5 is not designed to do complete virtual ISP in this manner (ie,
>The groups security was only designed for editing users (ie, limiting
>you can see).
>Dale E. Reed Jr. Emerald and RadiusNT
>IEA Software, Inc.
>For more information about this list (including removal) go to:

For more information about this list (including removal) go to: