No you don't have to. You HR people will be under HR company and will have unrestricted access. Others will be under Normal Non HR with restricted access to Non HR company only. Should work....
Regards, Aditya On Fri, Oct 12, 2012 at 3:02 AM, Pargeter, Christie :CO IS <cparg...@lhs.org > wrote: > ** > > But don’t you have to duplicate your People table under each company?**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Aditya Sharma > *Sent:* Thursday, October 11, 2012 2:07 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Multi-tenancy, Human resources, field ID 112 etc.**** > > ** ** > > ** Hi Ron,**** > > ** ** > > You can achieve this with multi-tenancy. You will need to > create separate compony for you HR users. Lets say your compony is Calbro, > the new company can be Calbaro-HR. All the foundation data corresponding to > your HR department should use this new company. You can have access > restriction set for users (Service Desk etc) to Calbro only (Add Calbro in > Access Restriction Tab of all the Calbro Users) so that cannot access > anything related to Calbro-HR compony. But vice versa you can set allow > your HR users to have access to Calbro as well as Calbro-HR companies (or > Give HR users Unrestricted Access if only two companies are there in your > system).**** > > ** ** > > Regards,**** > > Aditya **** > > On Thu, Oct 11, 2012 at 3:48 AM, Peters, Ron <rpet...@columbia.com> wrote: > **** > > ** **** > > Hi all,**** > > **** > > I believe we are currently running in multi-tenancy mode though we only > use a single company. Our help desk assigns tickets to various support > groups as normal. Now, were looking into bringing our HR department on > board so we can assign tickets etc. to them. I believe the main sticking > point is that they don’t want anyone seeing what could be sensitive > information in their tickets.**** > > **** > > I’ve heard that we can do something where only they see their tickets and > nobody else can. I’ve been reading about multi-tenancy and support > organizations but it wasn’t super clear about a situation like this. What > recommendations do you have for this type of scenario?**** > > **** > > We’re just starting down this path and are thinking about the > possibilities. These are some of the ones I’ve thought about but may not be > exhaustive (or correct for that matter).**** > > **** > > Most users should:**** > > Be able to assign tickets to HR users**** > > Not be able to see any of the HR tickets or ticket contents**** > > **** > > HR users should:**** > > Be able to assign their tickets back to non-HR groups, mainly service desk > but possibly others**** > > Be able to work their tickets.**** > > Probably be able to see non-HR tickets and contents**** > > **** > > Thoughts?**** > > **** > > Thanks,**** > > Ron**** > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > ** ** > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
