Share CMDB Data and allow Manual Updates to Certain Records

marc07
Tera Contributor

I have many individuals who want to use the CMDB for tracking information related to CI's. This means they need direct access and will need to change specific fields as well.  I also have IT Operations who want to add new and retire old CI's using the mobile application. How do I manage their access successfully and limit their ability to mess things up? Can I give them access to only certain CI groups? We're 6 months in to our CMDB deployment and already have a huge amount of pent-up demand and I want to this access to be as smooth as possible and the least risk to the CMDB.

Thanks for your insights into this.

1 ACCEPTED SOLUTION

Ashok Sasidhara
Tera Sage
Tera Sage

You should first discuss with all the CMDB stakeholders and finalize the list of CI owners for each CI class. Identify if there are any existing groups specifically associated with those CI owners. Create new groups if there are no existing relevant groups. Then provide the write access to each CI class only to the group which owns that class. Provide read access to other groups as needed.

For people who just need to validate the CI data periodically, you can use the 'data certification' feature and assign periodic data certification tasks to them for manual validation of key CI attributes. 

Also consider using the proposed changes feature explained below for all CI changes occuring as part of change management. The proposed data update will be automatically applied to CI when the change is implemented.

https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/configuration-management/co...

View solution in original post

2 REPLIES 2

Ashok Sasidhara
Tera Sage
Tera Sage

You should first discuss with all the CMDB stakeholders and finalize the list of CI owners for each CI class. Identify if there are any existing groups specifically associated with those CI owners. Create new groups if there are no existing relevant groups. Then provide the write access to each CI class only to the group which owns that class. Provide read access to other groups as needed.

For people who just need to validate the CI data periodically, you can use the 'data certification' feature and assign periodic data certification tasks to them for manual validation of key CI attributes. 

Also consider using the proposed changes feature explained below for all CI changes occuring as part of change management. The proposed data update will be automatically applied to CI when the change is implemented.

https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/configuration-management/co...

ersureshbe
Giga Sage
Giga Sage

Hi, I request you, its not support user work and it's part of Admin work. If changes required in CI class and attributes, Pls get the details using exist template (Download the template using import option selection from the table list view) and feed the data with the help of admins. When you are importing the CI data,  you should use import set table and define the unique id and additionally concentrate on IRE rules for each class.

Regards,
Suresh.