---
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


---

# Configuration identifiers framework

# Configuration identifiers framework {#ariaid-title1}

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

Configuration identifiers provide a framework that lets you customize some behaviors of a Service Graph Workspace feature, enabling different settings for that feature, on different workspaces. Most importantly, you can use this
customization framework when integrating a Service Graph Workspace feature into another workspace.

## Configuration identifier {#cnfg-identifiers-framework-sg__section_yfr_bwr_12c}

A configuration identifier (also referred to as config identifier) is a configuration element within the configuration identifiers framework. A config identifier contains custom settings for a Service Graph
Workspace feature, that is applicable to a specific workspace. A config identifier contains settings and table-driven configurations used in a UX application such as a workspace. Using config identifiers lets you for example, integrate
Service Graph Workspace Unified Map into another workspace, with the integrated Unified Map being customized for the workspace. Config identifiers are stored in the Config identifiers \[sn_cmdb_ws_config_identifier\] table.

A config Identifier acts as the parent record for a set of configurations that are specific to a workspace and therefore overrides default behavior only for that workspace.

## Default config identifier {#cnfg-identifiers-framework-sg__section_ggx_bwr_12c}

Initially, the Config identifiers \[sn_cmdb_ws_config_identifier\] table in Service Graph Workspace, contains a single config identifier named 'Default' and which is workspace-agnostic. This Default config identifier has its
Default column set to Yes, a setting that can't be modified. Only a single config identifier can be set to Yes, therefore, any additional config identifiers that you
create are set to No.

The default config identifier contains default settings for Service Graph Workspace features. Any subsequent Config Identifier that you configure, is set for a specific workspace. When integrating a Service Graph Workspace feature
into another workspace and there are no entries in the table-driven configuration for that feature, look-up uses the settings in the default configuration identifier.

## Key roles {#cnfg-identifiers-framework-sg__section_ypf_vfs_12c}

The following roles are needed in order to use the configuration identifiers framework:

* sn_cmdb_ws.config_editor: Can modify child config tables, such as sn_cmdb_ws_config_property.
* sn_cmdb_ws.config_admin: Can modify both sn_cmdb_ws_config_identifier and child config tables.
* sn_cmdb_admin: Role required to modify default config records under the default identifier or the default identifier itself.
{#cnfg-identifiers-framework-sg__ul_qbl_zfs_12c}

For more information about these roles, see [Components installed with Service Graph Workspace](https://servicenow-prod.fluidtopics.net/3ReYxIztpefnqToLR54_cQ "Several types of components are installed with the activation of the CMDB Workspace (sn_cmdb_ws) plugin, which includes Service Graph Workspace. This includes properties, tables, user roles, and scheduled jobs.").

## Examples of Service Graph Workspace features using the configuration identifiers framework for feature settings {#cnfg-identifiers-framework-sg__section_mtc_cwr_12c}

* Unified Map:
  * [Configure how many nodes can appear on a map](https://servicenow-prod.fluidtopics.net/rnBWaxFtdnnCoRkxos0dSQ "Configure the maximum number of nodes that can be loaded when a map in this workspace opens. These are general settings that only sn_cmdb_admin can configure.")
  * [Configure the default or maximum number of levels on maps](https://servicenow-prod.fluidtopics.net/0A6qC0VC8LZ~KmzzIRQ1sw "Configure the default or maximum number of levels on maps. These are general settings that only sn_cmdb_admin can configure.")
  * [Configure endpoint de-duplication on maps](https://servicenow-prod.fluidtopics.net/rRipajJogFfNQd_~TIXwEw "Configure how duplicate edges are displayed on maps. These are general settings that only sn_cmdb_admin can configure.")
  * [Configure which attributes to display in the Attributes panel](https://servicenow-prod.fluidtopics.net/FCLmy0fMsZbJq5ZOHZec_Q "Each class has a unique set of extended attributes that appear in the bottom section of the Attributes panel for a CI. For any class, you can specify which extended attributes should be displayed. These are general settings that only sn_cmdb_admin can configure.")
  * [Create a class profile of visible layers for classes](https://servicenow-prod.fluidtopics.net/_VWEBvUMqT5D3pHTxJijig "Configure a class profile that specifies which layers should appear for a particular class: application, service instance, business, or infrastructure. For example, you can configure that the mapped application service (service instance) [cmdb_ci_service_discovered] class should display only Service Mapping data and not infrastructure elements.")
  * [Configure CIs to appear based on life cycle stage value](https://servicenow-prod.fluidtopics.net/KNgPp3syd79xxGsXHeK1_Q "By default, only CIs for which Life cycle stage is Operational or empty appear on maps. You can configure the map to display CIs with other Life cycle stage values. These are general settings that only sn_cmdb_admin can configure.")
  {#cnfg-identifiers-framework-sg__ul_fpm_qzr_12c}
* Create CI:
  * [Request additional attributes for new CIs](https://servicenow-prod.fluidtopics.net/THPLmXUVNnzGtdcUytF1Nw "Integrate a request for specific CI attributes when manually creating a new CI in your workspace. Then, when creating a new CI in the respective workspace, users can enter values for the requested attributes, as appropriate for the new CI.")
  * [Limit the class list for new CIs created in a workspace](https://servicenow-prod.fluidtopics.net/LgCEcduu1qbOxdmjVFRJbw "Limit the selection of classes for a new CI being manually created in your workspace, to only those classes that are relevant to that workspace. When then creating a new CI in the respective workspace, users can only select a class that is authorized as an option.")
  {#cnfg-identifiers-framework-sg__ul_ipm_qzr_12c}
{#cnfg-identifiers-framework-sg__ul_dpm_qzr_12c}

