Plan and Prepare for your CMDB Implementation

Learn how to set up your Configuration Management Database (CMDB), assign the right permissions, and configure foundational settings to start using CMDB.

• Provision CMDB and Service Graph for IT Services
  Provision CMDB and Servicegraph to create the required CMDB environment and prepare your org for configuration. Provisioning creates a dedicated CMDB tenant and enables the required licenses, and services. Complete provisioning before configuring CMDB in Salesforce Go. Manual provisioning gives visibility into provisioning status and provides a clear recovery path if a previous attempt failed.
• Set Up CMDB Using Salesforce Go
  Swiftly set up your CMDB in just a few steps by using Salesforce Go. Use the guided setup experience to turn on the CMDB feature, discovery options, and configure data population rules. Reduce manual setup and unlock core CMDB functionalities with single activation flows.
• Permission Sets for CMDB
  The Configuration Management Database (CMDB) permission sets provide different levels of access. The number of permission set licenses in your Salesforce org depends on your license configuration and on how your solution is packaged. Permission set licenses entitle users to access features that aren’t included in their user licenses.
• Key Steps to Implement CMDB
  Understand the key steps to implement Salesforce CMDB & Service Graph from start to finish. Learn how to define configuration item (CI) types, manage CIs, organize CI attributes, and build reliable relationships between components. Set up your CMDB with clarity and avoid common setup issues. Using this structured approach to maintain consistent records, improve visibility, and ensure accurate asset data across your IT environment.
• Create a Default Account for Discovered Configuration Items Without an Owner
  Capture details about configuration items (CIs) that don’t have owner information by creating a default account. All assets found during the discovery process must be related to an Account ID or Contact ID, so the default account acts as a placeholder for the unassigned assets. This account is only used to create new assets. If an asset exists and matches a rule, the system updates the existing asset fields.