1. Help
  2. Asset Management & CMDB
  3. CMDB
  4. Getting Started with the CMDB
  1. Help
  2. Asset Management & CMDB
  3. CMDB
  4. Getting Started with the CMDB
purple icon for coordination.
We’ve moved!
Our Help Center has a new home and our URLs have changed. Please update your bookmark to this page before April 30, 2026

Getting Started with the CMDB

Set up and navigate the CMDB workspace, and find the right starting task.

The CMDB brings your configuration items, their relationships, asset lifecycle and financial attributes, and the data arriving from discovery and integrations into one workspace. This page orients you and points you to the right starting task.

The workspace

Open CMDB in the main navigation. The workspace has four tabs:

  • Dashboard: the CMDB Health dashboard, covering duplicate candidates, check-in freshness, field population, and relationship coverage.
  • Configuration Items: the inventory of every tracked instance, filterable by view and by Active or Inactive.
  • Reconciliation Queue: incoming records waiting to be matched or reviewed. The tab appears only while CI reconciliation is on.
  • Lifecycle Reviews: date-driven reviews for warranty, end-of-support, and refresh.

The setup screens live under Settings > CMDB: CI Rules, Reconciliation Rules, Products and Product Categories. Which entries you see depends on your role and plan, and Reconciliation Rules appears only while CI reconciliation is on.

A mental model

One way to hold it together: Product categories and products describe what things are. Configuration Items describe what you have. Rules and lifecycle reviews keep the data moving. CMDB Health tells you whether to trust it.

Start here

Pick the task that matches what you are trying to do:

Order matters

When you are setting the CMDB up from scratch, work outside in: categories before products, products before configuration items, and automation and reviews only once real data exists. Turning on reconciliation early is worth it, because it keeps the CMDB clean from the first integration onward rather than leaving you a duplicate queue to work later.