Jim, Multitenancy if setup properly is not a huge overhead and allows you to take advantage of a lot of the out of box functionality. Most implementations I have see setup multitenancy as separate organizations the are using the ITSM suite as almost a internal hosted solution for multiple support organizations. Most of them have a bunch of flaws in their setup. My guess is that you have multiple support organizations under a single customer that is looking to segregate data (soc, service desk, application development, noc, ect.). The best way to do this is multitenancy. It doesn't require customization and is simple configurations. What a log of developers I have see do is customize a solution because they want to do this at the support group level. Cool just build customizations around the permission fields I believe they are 112 and 6969. When assigned to a certain group set those fields at execution 999 to whatever group id that support group is. Now do this for every backend form that is going to touch. I'll be interested to see what final solution you come up with.
Brian -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rackley, James A CIV Sent: Tuesday, August 22, 2017 8:41 AM To: arslist@ARSLIST.ORG Subject: Re: [Non-DoD Source] Re: Securing Sensitive WO Information Roger is correct. Configuring multi-tenancy is not worth the ROI in this instance. Neither is Case Management. We were hoping for a simpler solution at the Support Group level. Regards, Jim -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Roger Justice Sent: Friday, August 18, 2017 4:14 PM To: arslist@ARSLIST.ORG Subject: [Non-DoD Source] Re: Securing Sensitive WO Information ** His statement is specific Support Group not separate companies. -----Original Message----- From: Deepak Pathak <dpathak1...@gmail.com> To: arslist <arslist@ARSLIST.ORG> Sent: Fri, Aug 18, 2017 3:52 pm Subject: Re: Securing Sensitive WO Information ** I believe that feature is called Multi-Tenancy. On Fri, Aug 18, 2017 at 10:34 AM, Rackley, James A CIV <james.a.rack...@uscg.mil> wrote: Oh Mighty Brain Trust, What is the recommended method to ensure that users with Work Order permissions CANNOT see a specific subset of WOs via Global Search, WO Console, Overview, AR Reporting, Analytics, or Smart Reporting? Essentially, only users in a specific Support Group should be able to see anything at all about WOs assigned to this Support Group. Thanks in advance! Regards, Jim Rackley, PMP CGFIXIT Service Manager USCG, C4ITSC, Business Operations Division "You can't help everyone. But everyone can help someone." _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.arslist.org&d=DwMCaQ&c=0NKfg44GVknAU-XkWXjNxQ&r=iuYYqFqKHbSOeyo5LY9dkV5F4FpNAQQwkv53Lj1KZMQ&m=bhbd2MzApvpTGxeBSWoFc2I-6QzdkhsaQKFVVHfXFuY&s=Me9JYEPDXPdI2JMa6-H17FULCBbOSVMPpO-lnzyqdD8&e=> "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" DISCLAIMER: The information contained in this e-mail and its attachments contain confidential information belonging to the sender, which is legally privileged. The information is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are notified that any disclosure, copying, distribution or action in reliance upon the contents of the information transmitted is strictly prohibited. If you have received this information in error, please delete it immediately. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
