RW & R are the only permissions available for customers X queues
Some of the scenarios you mentioned can be simulated by using ACLs
associated with the web UI. This is, however, something specific to the web
UI.
For example you can create an ACL that prevents the customer from closing a
ticket if
Correct me if I am wrong...
The RW permission is only to that group and extends to the queue
associated with that group. Hence, this allows a customer to open and
close cases in that queue. However, the other permissions are more
global like changes owenership, etc...
If this is right, is ther
It's not a proper use case. The customer should not have access to
those abilities, that is the job of an agent. A customer submits a
ticket and expects a response, he/she is agnostic to the process of
managing the ticket.
Steve
On 2 July 2013 02:39, Roman Gelfand wrote:
> While agent/group map
