That's working like a charm, thank you Ramana. This way, as expected in our model, the client sees only it's own main queue. There's just one more thing (for now :-) ) : despite there's just one possible queue for the client, he still has to select it. So, is there a way to auto-fill the queue field with this unique possible queue ? Thanks for any clue, Florian. -----Message d'origine----- De : otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] De la part de ramana Envoyé : mercredi 3 mars 2010 07:51 À : User questions and discussions about OTRS. Objet : [otrs] Hide the Required Queues on Customer frontend -- solutionfound. Hi Every one. IT is possible to hide the Required Queues on Customer frontend. IT is working fine for me. Solution : Hide the Required Queues on Customer frontend Add this script on ACL list $Self->{TicketAcl}->{'ACL-Customer-Queues'} = { Properties => {Frontend => {Action => ['CustomerTicketMessage'] }}, PossibleNot => { Ticket => { Queue => ['[RegExp]::', '[RegExp]^CHN-IT-L1', '[RegExp]^CHN-IT-L2', '[RegExp]^HYD-IT-L1', '[RegExp]^HYD-IT-L2', '[RegExp]^Junk', '[RegExp]^Misc', '[RegExp]^Raw', '[RegExp]^Postmaster',] } }}; Regards, Ramana --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/