Does it mean that one group doesn't want to see others' Incidents - Yes except Incidents submitted for shared Customers? Not even for shared customers. Can shared customers' incidents be assigned from one "separated' group to other? Yes specifically the new user process.
Thank you, Sandra Hennigan Remedy Developer From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Arkadiusz Bryndza Sent: Thursday, February 14, 2013 6:13 PM To: [email protected] Subject: Re: Multi-Tenancy Question ** Does it mean that one group doesn't want to see others' Incidents exept Incidents submited for shared Customers? Is it correct? Can shared customers' incidents be assigned from one "separated' group to other? Ark 2013/2/14 Hennigan, Sandra <[email protected]<mailto:[email protected]>> ** The problem is that no group wants another group to even see their Incidents. Thank you, Sandra Hennigan Remedy Developer From: Action Request System discussion list(ARSList) [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Arkadiusz Bryndza Sent: Tuesday, February 12, 2013 4:47 PM To: [email protected]<mailto:[email protected]> Subject: Re: Multi-Tenancy Question ** Looks like your definition of "separated" has changed. Previously, Operating Companies haven't seen each other's incidents. Now, they agree to share incidents (without permission to modify, only to view/report). Am I right? If it's correct then maybe it's good idea to drop multi-tenancy and convert Operating Companies to Support Organizations? 'Incident User' permission is used to allow to view incidents of other support groups but without ability to modify. Ark 2013/2/11 Hennigan, Sandra <[email protected]<mailto:[email protected]>> ** Any Multi-Tenancy gurus out there? ARS 8.0 Oracle 11g ITSM 8.0 Is there a way to share Customer People Records but completely segregate Incidents? We are using Multi-Tenancy and Operating Company to separate Business Units. Each Operating Company can only see their own People Records, tickets, CIs etc. Works well. Was working well. Except - Now the different Operating Companies want to share a Customer Company but still keep "their" tickets separate from each other Company. Scenario here: Support User Pete has access to his Operating Company and the Customer's Company - he can submit Incidents for either Company. His Operating Company Incidents are isolated away from other Operating Company's Incidents. He submits an Incident for the Customer's Company. If the Incident is assigned to his Operating Company, no other Operating Company has permission to modify the Incident BUT all other Operating Companies can view and report on the Customer Incident. Thank you, Sandra Hennigan Remedy Developer _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "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"
