Configuration Item Types (CI Types) categorizes CIs with similar properties. Any organization-specific entity can be considered as a CI Type, such as Business Services, Workstations, Servers, Documents, or the People working for your organization.
Role Required: SDAdmin and SDCMDBAdmin
Go to Setup > Customization > CMDB. You will see the CI Types list view.
The list view is in the form of a tree structure that displays the hierarchy of all available CI types and their descriptions.The CI types are arranged in the parent-child structure.
Click Expand/Collapse Tree on the toolbar to toggle the list view between fully expanded and fully collapsed views. Click
and
to view and hide the children CI types, respectively.
You can define new CI types to match your business needs. Click New CI Type on the list view.
The New CI Type form contains the following tabs:
Fill out the details as explained below:
|
Fields |
Explanation |
|
CI Type Name* |
Provide a name for the CI type. |
|
Parent CI Type* |
Select a parent type from the available list. |
|
API Name* |
Will be populated automatically based on the CI type name. You can still modify it. Enter the value in snake case consisting only of lowercase characters separated by an underscore. The API name will be prefixed by 'ci_' automatically. |
|
Description |
Describe the CI type. |
|
Icon |
Add an icon, if required. |
* mandatory fields
Click Save. You will be redirected to the Fields tab.

The Fields tab allows you to customize the layout of the CI Type form. It contains two sections: Canvas and Fields List.
The CI Type and Parent CI Type details are displayed at the top of the section.
|
Canvas |
The canvas is where you build a template. It contains two sections: Parent Fields
Child Fields
|
|
Fields List |
The field list on the right pane contains two tabs:
|
After configuring the fields, click Save.

Admin can define certain relationships between CI types, called the Suggested relationships. Admins decide the relationship type, the destination CI type, and the cardinality, based on the organization's requirements or policies. Child CI types inherit the relationships from parent and super parent CI types.
Adhere to the following rules while adding suggested relationships:
| Rule | Example |
|---|---|
|
Relationships are not possible between parent and child CI types. |
Consider the parent CI type 'Computer' and its child CI type 'Server'. While adding the relationship for 'Computer', the 'Server' option will be disabled under the Related CI Type picklist. |
|
Sibling to sibling relationships is possible. |
Assume, 'Workstation' and 'Server' are children of 'Computer'. You can create a relationship between 'Workstation' and 'Server'. |
|
Self-relationships are possible but; |
'Computer Backed up by Computer'. |
|
You cannot create more than one relationship between two CI Types using the same relationship type. This means only one combination of a Source CI Type, a Relationship Type, and a Related CI Type is possible. |
Consider the relationship 'Web Server Connected to IBM Workstation'. |
|
Conflicting suggested relationships are not allowed. |
Consider the suggested relationship 'User controls computer'. You cannot create 'Computer controls user' as another suggested relationship. |
|
Suggested relationships cannot be edited but can be deleted. |
|
|
If you delete a suggested relationship, the CI relationship created using this relationship will not be deleted, rather it will be treated as a custom relationship. |
|
To add relationships,
|
Field Name |
Description |
|
Source CI Type |
This field will already be set to the current CI type and cannot be edited. |
|
Relationship type* |
The type of relationship shared between the Source and Related CI types. This can be either direct or inverse. |
|
Choose a CI type from the hierarchy of all available CI types. |
|
|
Cardinality |
Cardinality is the property of a relationship between one CI type and another. The relationship can be one of the following:
If you do not choose a cardinality, the default value is taken as many to many. |
|
Display Options |
Enable the options as needed: Show this relationship as a separate tab - Enable this option to view the relationship as an individual tab in the CI details page. Hide this relationship in the map - Hide the relationship in the relationship map and business views. The relationship can still be viewed on the CI details page. |
* mandatory fields
.
to expand the view. You cannot edit or delete the parent relationships.

Sync rules define the data to be synced from assets, users, or software installations to CMDB.
to edit, delete, or run through a sync rule.From the CI types list view click the CI type or
> Edit beside the CI type to modify its details.
From the CI types list view click
> Delete beside the CI type.