Multitenancy is the best route to take. You could setup a support org and create a filter that locks the assignee group field down to that support org if you don't want to use multitenancy. Keep in mind that when locking down field 112 that the ticket is modified a few times once the ticket is saved, so you have to give the submitter access to the ticket as well. OOB submitter does not have permission to change a ticket.
Brian -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of R Johnston Sent: Tuesday, February 12, 2013 10:28 AM To: [email protected] Subject: Multiple Group vs Company Access On one of my systems i have a scenario where different companies want access to the system. The System does have multi-tenentcy in place (its 7.6) but currently no use for it. Currently only one company in ARS is used for all tickets with many teams having their own Support Groups that pass tickets around. The second company would like to use the system as well and be able to pass tickets from one company to the other - but i'm not allowed to let the companies see each others tickets (except for what they pass around). Within one company, can i limit someone to just seeing only what is assigned to their group (and avoid the whole multiple company mess) or is multi-tenentcy the way to go. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
