Re: How can we enable CI level access to users?
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
Re: How can we enable CI level access to users?
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
Re: How can we enable CI level access to users?
How about using account id field Atul Vohra On May 26, 2011, at 7:50 AM, Mahendra Mahalkar mahendra.mahal...@gmail.com wrote: ** 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 _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
Re: How can we enable CI level access to users?
Atul, Can account id provide CI type restriction? Can you please throw some light on it? ** ** ** ** *Regards,* *Mahendra Mahalkar* On Thu, May 26, 2011 at 3:58 PM, Atul Vohra a...@protechsoftwareinc.comwrote: ** How about using account id field Atul Vohra On May 26, 2011, at 7:50 AM, Mahendra Mahalkar mahendra.mahal...@gmail.com wrote: ** 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 _attend WWRUG11 www.wwrug.com ARSlist: Where the Answers Are_ _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
Re: How can we enable CI level access to users?
** This is covered in Chapter 1 - BMC Atrium 7.6 Administrator's Manual . Page 13.It discusses what you want to do and how to accomplish it.Terry On May 26, 2011, Mahendra Mahalkar mahendra.mahal...@gmail.com wrote: ** 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, MahendraMahalkar _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
Re: How can we enable CI level access to users?
Asset User permission will allow users to see all CI's that they are entitled to see according to your multi-tenancy setup. They will only be able to modify those that have a related support group to which they belong. Have you looked at using the normalisation engine to set CI permissions? 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are
Re: How can we enable CI level access to users?
The look at chapter 1 in Administrator guide page 13 and I found what I want. Thanks Terry. ** ** ** ** *Regards,* *Mahendra Mahalkar* On Thu, May 26, 2011 at 9:09 PM, Peter Romain p.romain.arsl...@parsolutions.co.uk wrote: Asset User permission will allow users to see all CI's that they are entitled to see according to your multi-tenancy setup. They will only be able to modify those that have a related support group to which they belong. Have you looked at using the normalisation engine to set CI permissions? 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 ___ 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
Re: How can we enable CI level access to users?
I haven't checked Normalization settings yet, but I am sure I can achieve by group/role permission model as explained in chapter 1 of administrative guide of CMDB. But still will check Normalization option so that in future it can give more flexibility. ** ** ** ** *Regards,* *Mahendra Mahalkar* On Thu, May 26, 2011 at 9:18 PM, Mahendra Mahalkar mahendra.mahal...@gmail.com wrote: The look at chapter 1 in Administrator guide page 13 and I found what I want. Thanks Terry. ** ** ** ** *Regards,* *Mahendra Mahalkar* On Thu, May 26, 2011 at 9:09 PM, Peter Romain p.romain.arsl...@parsolutions.co.uk wrote: Asset User permission will allow users to see all CI's that they are entitled to see according to your multi-tenancy setup. They will only be able to modify those that have a related support group to which they belong. Have you looked at using the normalisation engine to set CI permissions? 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 ___ 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
