Difference between revisions of "RT Permissions"
Jump to navigation
Jump to search
(more info) |
|||
| Line 21: | Line 21: | ||
# CreateTicket | # CreateTicket | ||
# ReplyToTicket | # ReplyToTicket | ||
| − | # '''DO NOT EVER''' give them any of the following: OwnTicket, StealTicket, TakeTicket (If you need to do | + | # '''DO NOT EVER''' give them any of the following: OwnTicket, StealTicket, TakeTicket (If you need to do use these, then use the Privileged group instead. There is no reason for somebody without an RT account to own a ticket and allowing ownership of tickets by unprivileged users requires the query builder to load the entire list of users who have ever sent mail to RT, drastically slowing it down.) |
[[Category: Howto]] | [[Category: Howto]] | ||
Revision as of 12:26, 24 May 2012
When creating a queue in RT, one must assign permissions to the users who should be able to access the queue. This is generally best done by giving Group Rights. The following are the standard (non-admin) rights given to the group (e.g. FGCore, FGStaff, Coders, ASS). Generally these rights would only be given to one group.
- CommentOnTicket
- CreateTicket
- ModifyTicket
- OwnTicket
- ReplyToTicket
- SeeQueue
- ShowACL
- ShowTicket
- ShowTicketComments
- StealTicket
- TakeTicket
- Watch
- WatchAsAdminCc
The special group Everyone should generally be given the following rights (so that they can send and receive email to RT regarding the ticket)
- CommentOnTicket
- CreateTicket
- ReplyToTicket
- DO NOT EVER give them any of the following: OwnTicket, StealTicket, TakeTicket (If you need to do use these, then use the Privileged group instead. There is no reason for somebody without an RT account to own a ticket and allowing ownership of tickets by unprivileged users requires the query builder to load the entire list of users who have ever sent mail to RT, drastically slowing it down.)