Hi Steve, if you don't have a requirement that you also want to restrict some people to show only tickets for one site, you can get away with using a separate customer_id per company.
If you DO have the requirement that some customers need to see only the tickets of one site, while others need to see the tickets for multiple sites, you DO need to use the multiple customer id´s per customer user, just as you found in the manual. I understand that this can become cumbersome if you have loads of custumer id's. ((enjoy)) Michiel Beijen R&D Follow me on Twitter: @otrsnl [https://twitter.com/otrsnl] OTRS AG Norsk-Data-Str. 1 61352 Bad Homburg GERMANY T: +31 (0) 6457 42418 F: +49 (0) 9421 56818-18 I: http://www.otrs.com Business Location: Bad Homburg, Country Court: Bad Homburg, HRB 10751, VAT ID: DE256610065 Chairman: Burchard Steinbild, Managing Board: André Mindermann GET OTRS::ITSM 2.0 NOW - including the brand new change management module! It´s the only ITIL® V3 compatible open-source IT Service Management solution certified by PinkVERIFY worldwide! - http://bit.ly/dv4CJF On Wed, May 19, 2010 at 9:16 PM, Steve Clark <[email protected]> wrote: > site 2. > Company A site 3. > ... > Company A site 300. > > We want to keep tickets by each site but allow one user at Company A HQ > to monitor all Tickets of Company A regardless of which site. > > As I understand it when we add to the customer_company table the > customer_id must be unique, and when we add to the customer_user > the customer_i --------------------------------------------------------------------- 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/
