---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Relationship governance rules

# Relationship governance rules {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Relationship governance rules is a set of relationship rules used to ensure consistency
and validity in modeling relationships between configuration items (CIs) in the CMDB. Use
relationship governance rules to prevent the selection of relationship types or directions that
are not allowed between specific CI types.
Different applications such as Discovery and Service Mapping create relationships between CIs. Each application might use inconsistent relationship type or direction to represent the same entity, resulting in multiple views of
the same CIs. Relationship governance rules define what are valid relationship types and valid directions between pairs of CI types resulting in valid and consistent relationships in the CMDB.  
Relationship governance rules consist of:

* [CMDB dependent relationship rules](https://servicenow-prod.fluidtopics.net/T8id5zOATdZQXqaWaqsSdw "Service definitions consist of CI types and relationship types. Dependent relationship rules define the dependency structure of the CI types and the relationship types in these service definitions, helping in CI identification and in the construction of business service maps."): Rules (hosting and containment rules) that are used for CI identification. You can view and modify dependent relationship rules in the CI Class Manager, after selecting a class from the class hierarchy and clicking Dependent Relationship.
* [Suggested relationships](https://servicenow-prod.fluidtopics.net/OoBI1VhSW4w8Op7UJUmtpQ "The system keeps a table (Suggested Relationship [cmdb_rel_type_suggest]) of relationship types that are appropriate for a CI type, based on its class. You can manage suggested relationships by navigating to Configuration > Suggested Relationships , or in the CI Class Manager."): Rules that are based on existing suggested relationships in the Suggested Relationship \[cmdb_rel_type_suggest\] table. Suggested relationships are used in the [CI relationship editor](https://servicenow-prod.fluidtopics.net/ZYSoLQhMhfP~0mfvN~Okxg "Use the relationship editor to view, create, modify, or delete CI relationships. Open the relationship editor from the CI Relations formatter."). You can view and modify suggested relationships in the CI Class Manager, after selecting a class from the class hierarchy and clicking Suggested Relationships.
* [Reference rules](https://servicenow-prod.fluidtopics.net/T8id5zOATdZQXqaWaqsSdw "Service definitions consist of CI types and relationship types. Dependent relationship rules define the dependency structure of the CI types and the relationship types in these service definitions, helping in CI identification and in the construction of business service maps."): Rules that are used mostly by Cloud Management to represent all the possible valid combinations of pairs of referencing and referenced CIs in the service definition.
* Built-in valid relationships: The following relationships are pre-defined in the base system as valid relationships:
  * cmdb_ci_endpoint -\> Applicative Flow To::Applicative Flow From -\> cmdb_ci_endpoint
  * cmdb_ci_endpoint -\> Implement End Point To::Implement End Point From -\> cmdb_ci
  * cmdb_ci -\> Use End Point To::Use End Point From -\> cmdb_ci_endpoint
  {#relationship-governance__ul_s2l_5jx_j2b}
{#relationship-governance__ul_q5y_pyr_32b}

## General behavior {#relationship-governance__section_uwf_br5_j2b}

* Relationship governance rules support inheritance. For example, suppose that the
  suggested relationship cmdb_ci_appl Runs On::Runs cmdb_ci_hardware exists. Then a Runs
  On::Runs relationship between a cmdb_ci_appl_dot_net CI and a cmdb_ci_windows_server CI is
  valid. That is because .Net Application class inherits from the Application class and the
  Windows Server class inherits from the Hardware class.

* Duplicate relationship governance rules are not allowed.
* Relationship governance rules are not domain separated.
* It is allowed to have more than one relationship type between the same two CI types.  
  For example, the following relationships are valid:
  * cmdb_ci_appl Depends On::Used by cmdb_ci_service
  * cmdb_ci_appl Receives data from::Sends data to cmdb_ci_service
  {#relationship-governance__ul_bdj_lfx_j2b}
{#relationship-governance__ul_en5_hzr_32b}

## Reports {#relationship-governance__section_qgl_bbx_j2b}

A relationship between CIs is considered valid if it conforms to any of the relationship governance rules. Use the Relationship Health Dashboard to view reports about [relationships health](https://servicenow-prod.fluidtopics.net/~UsBq4S3pbt~Xyj7SGMU1A "View health scores for relationship health such as orphan, stale, and duplicate relationships, in the Relationship Health Dashboard.") including relationships compliance with relationship governance rules. The 'Relationships not compliant with all relationship rules' report shows CI relationships
that are not compliant with any of the relationship governance rules.
**Zugehörige Konzepte**   

* [CI relations formatter](https://servicenow-prod.fluidtopics.net/GGwZ5tBNNPR7wrMvRM6kpg "The default CI form includes a CI relations formatter from which you can examine a CI and its relationships in various views. From the CI relations formatter, you can also launch the CI relationship editor for the CI.")
* [CI relationship editor](https://servicenow-prod.fluidtopics.net/ZYSoLQhMhfP~0mfvN~Okxg "Use the relationship editor to view, create, modify, or delete CI relationships. Open the relationship editor from the CI Relations formatter.")
* [Relation qualifier](https://servicenow-prod.fluidtopics.net/fnPnt~tnrQy3ujI4atQamg "A relation qualifier, which is a CI of the Qualifier [cmdb_ci_qualifier] type, stores important information about the CI relationships.")
* [CI relationship security](https://servicenow-prod.fluidtopics.net/suP5YlmGdlhvvOa1kSMTpA "When applying security to CI relationships, it is important to apply the access controls both to the CI Relationship (cmdb_rel_ci) table and to create an operation editCIRelations to the * table as well.")  
**Zugehörige Tasks**   

* [Add a suggested relationship](https://servicenow-prod.fluidtopics.net/cGhMCk5TIPRt5Xu~9AJk8g "Add a suggested relationship for a class. The list of suggested relationships for a class is available when you create a new relationship for a CI of that class.")
* [Create a CI relation rollup](https://servicenow-prod.fluidtopics.net/O1O39DN5dXIOww_9ObiXmg "A CI relation rollup allows you to sum, count, max, min, or mean a relationship type. You can create CI relation rollups.")  
**Zugehörige Verweise**   

* [Suggested class relationships](https://servicenow-prod.fluidtopics.net/OoBI1VhSW4w8Op7UJUmtpQ "The system keeps a table (Suggested Relationship [cmdb_rel_type_suggest]) of relationship types that are appropriate for a CI type, based on its class. You can manage suggested relationships by navigating to Configuration > Suggested Relationships , or in the CI Class Manager.")

