Re: Securing an output queue

Hmmm.... If my solution works you owe me a beer :-)

OK, everybody needs to be able see DEPTUSR's data, but is it also important that UserA not be able to see UserB's data, UserB cannot see UserA's data?

If User A and B can see each other's data, solution is easy. If not, solution is more difficult....

let me know.

jte


On Apr 21, 2010, at 3:55 PM, Lance Gillespie wrote:

I would like to do just the opposite -
give a group of users that have no special security
and can now only see their own spool files the
ability to see the spool files created by one additional
user id, call it DEPTUSER.

The result would be that each of these individuals would
still have full control of their own spool files and would
also be able to control any spool files created by DEPTUSER,
without also being able to control each others.

If need be, I can create an out queue and make all of DEPTUSER's
files go there, but I don't see that helping.

Thanks,
Lance

--
John Earl
President and CEO
Patrick Townsend Security Solutions
"The Encryption Company"

Olympia, WA | www.patownsend.com
Office: 360-357-8971 Ext 118