Schultz, Eric wrote:
If they have not rights granted, then I am not sure why they are
seeing it, unless the people who are able to see it are members of
another group that does have the privileges. The priv system is
pretty straightforward, you shouldn’t have too much trouble. By
default, nobody has any access to a brand new queue, you have to
explicity add the access. At least, this is true for 3.4.x. Are you
running a different version, perhaps?
I’m running 3.4.4.
I’ve created a new queue and it is visible to anyone in the
priviledged group by default.
Maybe there’s a configuration option that does that (include rights for
the priviledged group to any new queue).
I’ll have to work it out.
Any other suggestions appreciated.
Thanks for your help.
*From:* Luke Vanderfluit [mailto:email@example.com]
*Sent:* Tuesday, January 31, 2006 2:41 PM
*To:* Schultz, Eric
*Subject:* Re: [rt-users] secret queues with restricted access
That sounds great.
Schultz, Eric wrote:
Sure. Just don’t give the default groups (Everyone, Unprivileged,
Privileged) SeeQueue or ShowTicket or anything like that. That’s the
nice thing about the RT ACLs is that they start very restrictive, and
you can ease it as much as you want. It won’t show up in Quick Search
or in “New ticket in” or anything like that for anyone but those you
explicitly give permission to.
I have an existing queue 'test' that has all those groups showing
'no rights granted'
How can I remove the rights that they have, if I wanted to
restrict the 'test' queue to only a few users or just one group?
It seems that by default the groups you mentioned *have* the
rights to view the 'test' queue.
Hope this can be done.
[mailto:firstname.lastname@example.org] On Behalf
Of Luke Vanderfluit
Sent: Tuesday, January 31, 2006 2:12 PM
Subject: [rt-users] secret queues with restricted access
I want to create a queue that is not visible to the bulk of RT users.
Only a few.
So only a select number of users will have access AND be able
to see the
That means it should only show up in a queue listing for
I’m sure this can be done with a customised script but can it be done
with existing config options?
Thanks for any help.