Thanks Peter. Asset user permission will allow all the groups to see/modify all the CIs, not the specific CI type. The version and modules are ARS 7.6.04 and Asset, CMDB, IM, PM,CM.
** ** ** ** *Regards,* *Mahendra Mahalkar* On Thu, May 26, 2011 at 3:24 PM, Peter Romain < p.romain.arsl...@parsolutions.co.uk> wrote: > What do you mean by restrict? > > What versions and what modules do you have? > > Multi-tenancy can be used to restrict CI's that users see but this will > probably be no good for you as it will also restrict access to tickets. > > You can give users asset user permission which will only allow them to see > all CI's but only modify CI's that have a people relationship to a group > they belong to. > > The normalisation engine in 7.6.4 can add permissions to CI's so you could > investigat if this gives you what you want. > > Cheers > > Peter > > > > Hi, > > I have been aske to restrict support group level access to CIs. Is this > > recommended? > > e.g SG1 will handle Computer system, SG2 can handle Software systems and > > related licenses. > > so SG1 should have access to comp systems only and not software systems. > > I checked CI clases and permissions in classes while > creation/modification > > of a class can be updated, can we update them by placing groups for SG1 > > and > > SG2? > > ** > > ** > > ** > > ** > > *Regards,* > > *Mahendra Mahalkar* > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
