---
title: Reference - CI/CD object types
---
> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).
The [Continuous Integration](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/continuous-integration.md) and [Continuous Deployment](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/continuous-deployment.md) features support the following types of Xperience objects:
Related pages
- [Continuous Integration](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/continuous-integration.md)
- [Continuous Deployment](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/continuous-deployment.md)
- [CI/CD repository structure](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/ci-cd-repository-structure.md)
- [Exclude objects from CI/CD](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md)
## General
| Object type | CI/CD folder name | Notes |
| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AIRA artifacts | aira.artifact | Stores artifacts created by AIRA agents, such as the [Content Strategist](https://docs.kentico.com/documentation/business-users/aira/agentic-marketing-suite.md#content-strategist) agent.
CI/CD stores an XML file for the base artifact object. The content of the artifact is stored as a separate file next to the XML file. |
| [Alternative forms](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md#define-editing-forms) | cms.alternativeform | Used by the Xperience administration. Contains definitions of UI forms used to provide editing interfaces for [object types](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md).
Child object type of **Module class** objects. |
| [Channels](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md) | cms.channel | A medium for delivering content via a specific method (website, email, social networks). |
| [Consents](https://docs.kentico.com/documentation/developers-and-admins/data-protection/consent-management.md) | cms.consent | Includes consent definitions, with all consent texts. CI/CD does not include archived consents or consent agreements given by contacts. |
| [Languages](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md) | cms.contentlanguage | |
| Modules | cms.resource | Contains definitions for system and [custom modules](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md#define-the-data-class). Direct parent of module class (cms.class) objects.
Supported child objects:
Module classes (cms.class) |
| Module classes | cms.class | Includes the definitions and settings of module classes ([object types](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types.md)). Used internally by the Xperience administration and data structure.
Supported child objects:
Alternative forms (cms.alternativeform) |
| Module classes - Customizable | cms.systemtable | Includes the definitions and settings of [extendable system object types](https://docs.kentico.com/documentation/developers-and-admins/customization/object-types/extend-system-object-types.md). These are system classes that can be customized with additional fields and columns, such as Customer, Order, Contact, User, and others.
Supported child objects:
Alternative forms (cms.alternativeform)
Queries (cms.query) |
| [Member roles](https://docs.kentico.com/documentation/developers-and-admins/development/registration-and-authentication/member-roles.md) | cms.memberrole | Definitions of member roles used for role-based content security. |
| [Notification emails](https://docs.kentico.com/documentation/developers-and-admins/configuration/notifications.md) | cms.notificationemail | |
| [Notification email templates](https://docs.kentico.com/documentation/developers-and-admins/configuration/notifications.md#notification-email-templates) | cms.notificationemailtemplate | |
| Queries | cms.query | Used internally by the system.
Child object type of **Module class** objects. |
| [Roles](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management.md) | cms.role | |
| [Scheduled task](https://docs.kentico.com/documentation/developers-and-admins/customization/scheduled-tasks.md) configurations | cms.scheduledtaskconfiguration | Information about scheduled task execution intervals and other metadata. |
| Setting categories and groups | cms.settingscategory | The _cms.settingscategory_ object type includes both setting categories and setting groups. |
| [Settings](https://docs.kentico.com/documentation/developers-and-admins/configuration/settings.md) | cms.settingskey | Settings are supported, but _**excluded by default**_ in the [repository.config file](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md). Settings may contain sensitive data – only remove the exclusion if you agree to make setting values available within the file system used by your application and any connected source control systems. You can configure the _repository.config_ file to include settings in general, but exclude individual setting keys that you consider sensitive.
**Important:** The **License key** (_Settings_ -> _System_ -> _Licenses_) setting that stores the [license key](https://docs.kentico.com/documentation/developers-and-admins/installation/licenses.md#license-keys) used to activate the instance is excluded permanently regardless of your _repository.config_ configuration. |
| [Users](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/user-management.md) | cms.user | User accounts for the administration interface. |
| [Workspaces](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/workspaces.md) | cms.workspace | When using CI/CD to add a new workspace, your [repository configuration](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md) must also include the _cms.contentfolder_ object type. Each workspace requires a root content folder to ensure that [Content hub](https://docs.kentico.com/documentation/business-users/content-hub.md) works correctly. |
## Content management
| Object type | CI/CD folder name | Notes |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Content types](https://docs.kentico.com/documentation/developers-and-admins/development/content-types.md) | cms.contenttype | Stores content type definitions. |
| [Content items](https://docs.kentico.com/documentation/business-users/content-hub.md) | contentitemdata.\*
cms.contentitem
cms.contentitemcommondata
cms.contentitemlanguagemetadata | The system uses multiple files to store content item data. See the **Content items** section of [CI/CD repository structure](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/ci-cd-repository-structure.md#content-items) for more information.
**Important:** To include or exclude content items from the repository, use the `IncludedContentItemsOfType` or `ExcludedContentItemsOfType` [filters](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md#includeexclude-content-items). ([Available from Xperience 30.4.0](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories/config-v2-migration.md))---
CI/CD data does **not include** changes made to new versions of previously published content items. While an item is in the _Draft (New version)_ status (or a custom [workflow step](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md)), CI/CD stores the original published version, until the new changes are published. Consequently, the **published** version of content items is always restored by CI/CD – any changes made in _Draft (New version)_ or custom workflow steps are **lost** when the item is restored.---
If you are only changing content item data (and not the schema/structure), consider using [Content sync](https://docs.kentico.com/documentation/business-users/content-sync.md) instead of continuous deployment. If you must use CD to group item deployments, ensure all parent content types are [whitelisted](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md#scope-filtering-with-the-objecttype-attribute) in your configuration.---
**Content item asset fields**
Binary data managed by [fields](https://docs.kentico.com/documentation/developers-and-admins/customization/field-editor.md) of the _Content item asset_ data type is serialized into the repository together with the source content item objects – on instances using CI/CD, the binary data exists in two copies: one in the _\~/assets_ folder and the second in the repository.
**Note**: Changing the data type of _Content item asset_ fields or removing these fields entirely will result in abandoned binary files in the repository. To remove these unwanted files, serialize all objects again, which recreates the repository without the orphaned files. |
| [Content folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md#content-folders) | cms.contentfolder | Stores folders used to organize items in the _Content hub_ application. Required for all projects to ensure that the content hub works correctly.
The CI/CD files storing content hub folder data are organized into file system subfolders named according to each content hub folder's parent. The hierarchy starts from a "root" system folder.
[Smart folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md#smart-folders) are stored separately as _cms.smartfolder_ objects. |
| [Headless channel configuration](https://docs.kentico.com/documentation/developers-and-admins/configuration/headless-channel-management.md) | cms.headlesschannel | Child object type of **Channel** objects. |
| [Headless items](https://docs.kentico.com/documentation/business-users/headless-content.md) | contentitemdata.\*
cms.contentitem
cms.contentitemcommondata
cms.contentitemlanguagemetadata
cms.headlessitem | The system uses multiple files to store headless item data. See the **Headless items** section of [CI/CD repository structure](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/ci-cd-repository-structure.md#headless-items) for more information.
**Important:** To include or exclude headless items from the repository, use the `IncludedContentItemsOfType` or `ExcludedContentItemsOfType` [filters](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md#includeexclude-content-items). ([Available from Xperience 30.4.0](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories/config-v2-migration.md))---
CI/CD data does **not include** changes made to new versions of previously published headless items. While an item is in the _Draft (New version)_ status (or a custom [workflow step](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md)), CI/CD stores the original published version, until the new changes are published. Consequently, the **published** version of headless items is always restored by CI/CD – any changes made in _Draft (New version)_ or custom workflow steps are **lost** when the item is restored. |
| [Media library files](https://docs.kentico.com/documentation/business-users/media-libraries/manage-media-files.md) | media.file | Child object type of **Media library** objects.
Only includes media file definitions, not the binary data of individual media files. Binary data is stored on the file system in the media library folders. |
| [Pages](https://docs.kentico.com/documentation/business-users/website-content.md) | contentitemdata.\*
cms.contentitem
cms.contentitemcommondata
cms.contentitemlanguagemetadata
cms.webpageitem | The system uses multiple files to store page data. See the **Pages** section of [CI/CD repository structure](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/ci-cd-repository-structure.md#pages) for more information.
**Important:** To include or exclude pages from the repository, use the `IncludedContentItemsOfType` or `ExcludedContentItemsOfType` [filters](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md#includeexclude-content-items). ([Available from Xperience 30.4.0](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories/config-v2-migration.md))---
CI/CD data does **not include** changes made to new versions of previously published pages. While a page is in the _Draft (New version)_ status (or a custom [workflow step](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md)), CI/CD stores the original published version, until the new changes are published. Consequently, the **published** version of pages is always restored by CI/CD – any changes made in _Draft (New version)_ or custom workflow steps are **lost** when the page is restored.
CI/CD data also does **not include** changes made to [page permissions](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/page-permission-management.md). After performing the CD restore operation, the moved and newly created pages inherit permissions from their new parent page.---
Supported child objects:
[Page former URL paths](https://docs.kentico.com/documentation/business-users/website-content/manage-page-urls.md#former-urls) (cms.webpageformerurlpath)
[Page URL paths](https://docs.kentico.com/documentation/business-users/website-content/manage-page-urls.md) (cms.webpageurlpath) |
| [Page former URL paths](https://docs.kentico.com/documentation/business-users/website-content/manage-page-urls.md#former-urls) | cms.webpageformerurlpath | Child object type of **Page** objects. |
| [Page URL paths](https://docs.kentico.com/documentation/business-users/website-content/manage-page-urls.md) | cms.webpageurlpath | Child object type of **Page** objects. |
| Web page folders | ##WebPageFolders## | **Important:** Dedicated mechanism for including/excluding website channel folders was introduced starting with [v2 configuration files](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories/config-v2-migration.md) available from version 30.4.0.
Website channel folders that are used to group pages in the content tree. They are represented as regular content items but have no backing content type structure. To track these folders in CI/CD repositories, use the _##WebPageFolders##_ placeholder instead of a regular content type inside the `` or `` elements.
` ##WebPageFolders## ` |
| [Preset page templates](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder/page-templates-for-page-builder.md) | cms.pagetemplateconfiguration | The Page Builder configuration of a saved preset page template created using a default page template. |
| [Reusable field schemas](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md) | cms.class | Reusable field schema definitions and data are stored as part of the _cms.contentitemcommondata_ object type.
If your [content types](#cicd_contenttypes) use reusable field schemas and you want to track changes to their structure and data, you must serialize _cms.contentitemcommondata_ into your repository. This is particularly relevant for [SaaS](https://docs.kentico.com/documentation/developers-and-admins/saas.md) projects that need to explicitly opt-in for each CI/CD object.
Tracking reusable field schemas in CI/CD requires the following includes in _repository.config_.
` cms.class
CMS.ContentItemCommonData `**Note:** **cms.resource filtering**
The [cms.resource](#cms-resource) object type is a direct parent of all _cms.class_ object types.
If your _repository.config_ [includes or excludes](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md) a subset of _cms.resource_ objects, you need to explicitly include the **CMS.ContentEngine** resource to enable _cms.contentitemcommondata_ serialization.
`
CMS.ContentEngine `
After including the resource, run the store operation again to serialize it to your repository. |
| [Smart folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md#smart-folders) | cms.smartfolder | Stores smart folders, which are used to dynamically categorize and filter items in the _Content hub_ application.
The [content folder](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md#content-folders) hierarchy in the _Content hub_ application is stored separately using _cms.contentfolder_ objects. |
| [Taxonomies](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md) | cms.taxonomy | |
| [Tags](https://docs.kentico.com/documentation/developers-and-admins/configuration/taxonomies.md) | cms.tag | Tags that belong under another tag in the taxonomy tree are stored as child objects in the CI/CD repository. CI/CD files representing child tags are placed under subfolders named according to the parent tag. |
| [Web page scope](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/limit-the-pages-users-can-create.md) | cms.webpagescope | Child object type of **Website channel configuration** objects. |
| [Website channel configuration](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md) | cms.websitechannel | Child object type of **Channel** objects. |
| [Workflows](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md) | cms.contentworkflow | Supported child objects:
Workflow step (cms.contentworkflowstep) |
| Workflow step | cms.contentworkflowstep | Child object type of **Workflow** (cms.contentworkflow) objects. |
## Digital marketing
| Object type | CI/CD folder name | Notes |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Activity types](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/set-up-activities.md) | om.activitytype | |
| [Automation processes](https://docs.kentico.com/documentation/business-users/digital-marketing/automation.md) | ma.automationprocess | Stores automation processes. CI/CD data does **not include** information about contacts passing through automation processes, or the contact history and other statistics of automation steps.
Also required to ensure the functionality of all types of [form autoresponders](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#actions-after-form-submission), which internally use automation.
Note: If you delete or significantly restructure the steps in a process, and then CI/CD restore these changes on an instance where the process is already enabled or has contact history, you may break the process or cause inconsistencies. This scenario is **not supported**.
Supported child objects:
Automation steps (ma.automationstep)
Automation triggers (cms.objectworkflowtrigger) |
| Automation actions | ma.automationaction | Stores data representing the step types that perform specific actions within automation processes (e.g., "Send email").
Also required to ensure the functionality of all types of [form autoresponders](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#actions-after-form-submission), which internally use automation.
Required for all projects to ensure system functionality that internally uses automation processes. |
| Automation steps | ma.automationstep | Stores steps within automation processes (Automation Builder). CI/CD data does **not include** information about contacts passing through automation processes, or the contact history and other statistics of automation steps.
Also required to ensure the functionality of all types of [form autoresponders](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#actions-after-form-submission), which internally use automation.
Note: If you delete or significantly restructure the steps in a process, and then CI/CD restore these changes on an instance where the process is already enabled or has contact history, you may break the process or cause inconsistencies. This scenario is **not supported**.
Child object type of **Automation process** objects. |
| Automation triggers | cms.objectworkflowtrigger | Stores the triggers of automation processes.
Also required to ensure the functionality of all types of [form autoresponders](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md#actions-after-form-submission), which internally use automation.
Child object type of **Automation process** objects. |
| [Campaigns](https://docs.kentico.com/documentation/business-users/digital-marketing/campaigns.md) | om.campaign | Stores campaign data and references to campaign assets. |
| [Contact groups](https://docs.kentico.com/documentation/business-users/digital-marketing/contact-groups.md) | om.contactgroup | Only includes the definitions of contact groups, without information about the contacts assigned to the groups.
Additionally, the CI/CD data does not contain information about scheduled rebuilds for contact groups. After restoring a new condition-based contact group from the repository folder, you need to manually rebuild the group in the _Contact groups_ application. |
| Countries | cms.country | Supported child objects:
States (cms.state) |
| [Customer journeys](https://docs.kentico.com/documentation/business-users/digital-marketing/customer-journeys.md) | om.customerjourney
om.customerjourneyhistory | Only includes the definitions of customer journeys, without statistics calculated for contacts.
When restoring a customer journey from the repository folder, make sure to include module classes (_cms.class_). After the restoration, you need to manually [recalculate](https://docs.kentico.com/documentation/business-users/digital-marketing/customer-journeys.md#customer-journey-results) the journey in the Customer journeys application.
Supported child objects:
Customer journey stages (om.customerjourneystage) |
| Customer journey stages | om.customerjourneystage | Child object type of **Customer journey** objects. |
| [Email channel configuration](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-channel-management.md) | emaillibrary.emailchannel | Supported child objects:
Email channel sender address (emaillibrary.emailchannelsender) |
| Email channel sender addresses | emaillibrary.emailchannelsender | Child object type of **Email channel configuration** objects. |
| [Emails](https://docs.kentico.com/documentation/business-users/digital-marketing/emails.md) | contentitemdata.\*
cms.contentitem
cms.contentitemcommondata
cms.contentitemlanguagemetadata
emaillibrary.emailconfiguration | The system uses multiple files to store email data. See the **Emails** section of [CI/CD repository structure](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/ci-cd-repository-structure.md#emails) for more information.
Supported child objects:
Regular email sendout configuration (emaillibrary.sendconfiguration)
**Important:** To include or exclude emails from the repository, use the `IncludedContentItemsOfType` or `ExcludedContentItemsOfType` [filters](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories.md#includeexclude-content-items). ([Available from Xperience 30.4.0](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/configure-ci-cd-repositories/config-v2-migration.md))---
CI/CD data does **not include** changes made to new versions of previously published emails. While an email is in the _Draft (New version)_ status (or a custom [workflow step](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md)), CI/CD stores the original published version, until the new changes are published. Consequently, the **published** version of emails is always restored by CI/CD – any changes made in _Draft (New version)_ or custom workflow steps are **lost** when the email is restored.
Does not include [statistics](https://docs.kentico.com/documentation/business-users/digital-marketing/emails/track-email-statistics.md) tracked for emails. |
| [Email templates](https://docs.kentico.com/documentation/business-users/digital-marketing/emails.md) | emaillibrary.emailtemplate | |
| [Forms](https://docs.kentico.com/documentation/business-users/digital-marketing/forms.md) | cms.form
cms.formclass | Only includes form definitions and settings, not the data records stored by individual forms.
The system uses multiple object types to store the definitions and settings of forms. See the **Forms** section in [CI/CD repository structure](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/ci-cd-repository-structure.md) for more information. |
| Form featured fields | cms.formfeaturedfield | Stores the definitions of fields displayed in the **Featured** category when [adding fields to forms](https://docs.kentico.com/documentation/business-users/digital-marketing/forms/create-and-edit-forms.md). |
| [Identity resolution rules](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform/identity-resolution.md) | om.identityresolution | Stores identity resolution rules for profile merging when [customer data platform](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform.md) is enabled. |
| Macro rules | cms.macrorule | Used internally for the condition builder in [contact groups](https://docs.kentico.com/documentation/business-users/digital-marketing/contact-groups.md), [customer journeys](https://docs.kentico.com/documentation/business-users/digital-marketing/customer-journeys.md) and [automation processes](https://docs.kentico.com/documentation/business-users/digital-marketing/automation.md). |
| Macro rule categories | cms.macrorulecategory | Used internally for the condition builder in [contact groups](https://docs.kentico.com/documentation/business-users/digital-marketing/contact-groups.md), [customer journeys](https://docs.kentico.com/documentation/business-users/digital-marketing/customer-journeys.md) and [automation processes](https://docs.kentico.com/documentation/business-users/digital-marketing/automation.md). |
| [Preset email templates](https://docs.kentico.com/documentation/business-users/digital-marketing/emails/create-emails-in-email-builder/email-builder-templates.md) | emaillibrary.emailpresettemplate | The Email Builder configuration of a saved preset email template created using a default email template. |
| [Recipient lists](https://docs.kentico.com/documentation/business-users/digital-marketing/emails/send-regular-emails-to-subscribers.md) | om.recipientlist | Stores recipients lists, which contain contacts who opt in to receive regular emails. Only includes the recipient list definition, without information about the contained recipients.
Supported child objects:
Recipient list settings (emaillibrary.recipientlistsettings) |
| Recipient list settings | emaillibrary.recipientlistsettings | Stores the approval and unsubscribe settings of recipient lists.
Child object type of **Recipient list** objects. |
| [Regular email sendout configuration](https://docs.kentico.com/documentation/business-users/digital-marketing/emails/send-regular-emails-to-subscribers.md) | emaillibrary.sendconfiguration | Child object type of **Email** objects (emaillibrary.emailconfiguration). |
| [Segments](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/customer-data-platform/segments.md) | om.segment | Only includes the definitions of segments, without information about the assigned profiles.
Additionally, the CI/CD data does not contain information about scheduled recalculation of segments. After restoring a new segment from the repository folder, you need to manually recalculate the segment in the _Segments_ application. |
| States | cms.state | Child object type of **Country** objects. |
| [Tracked websites](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/cross-site-tracking.md) | om.trackedwebsite | Websites registered for the [Cross-site tracking](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/cross-site-tracking.md) feature. |
## Digital commerce
| Object type | CI/CD folder name | Notes |
| ----------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Order status | commerce.orderstatus | Represents [statuses](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/configure-order-statuses.md) in the lifecycle of orders created by customers (_New_, _Payment received_, _Shipped_, _Delivered_, etc.). |
| Shipping method | commerce.shippingmethod | Defines [shipping options](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/shipping-and-payment-methods.md) available to customers during checkout. |
| Payment method | commerce.paymentmethod | Defines [payment options](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/shipping-and-payment-methods.md) available to customers during checkout. |
| Promotion | commerce.promotion | Stores created [promotions](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/promotions.md). |
| Promotion coupons | commerce.promotioncoupon | Stores [coupon codes](https://docs.kentico.com/documentation/developers-and-admins/digital-commerce-setup/promotions/coupon-codes.md) associated with created promotions. |
## Binding object types
In addition to standard object types, CI/CD also supports most related bindings (i.e. objects representing relationships between the supported objects and other objects).
| Binding | CI folder name | Main object type (parent) | Related object type |
| ----------------------------------------- | ------------------------------------------ | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Allowed child content types | cms.allowedchildcontenttype | Content type | Content type |
| Application permissions | cms.applicationpermission | Role | No regular object type. The binding connects roles to application identifiers (defined in code when registering an admin UI application) and permission identifiers (defined in code when specifying the set of permissions available for an application). |
| Automation process step transitions | cms.workflowtransition | Automation step | Automation step |
| Allowed content types for channels | cms.contenttypechannel | Channel | Content type |
| Allowed email templates for content types | emaillibrary.emailtemplatecontenttype | Content type | Email template |
| Email sendout contact group configuration | emaillibrary.sendconfigurationcontactgroup | Regular email sendout configuration | Contact group |
| Macro rules assigned to categories | cms.macrorulemacrorulecategory | Macro rule category | Macro rule |
| Order status notification users | commerce.orderstatusnotification | Order status | User |
| Users in roles | cms.userrole | Role | User |
| Web page scope content type | cms.webpagescopecontenttype | Web page scope | Content type |
| Workflow content type | cms.contentworkflowcontenttype | Content workflow | Content type |
| Workflow roles with full control | cms.contentworkflowrole | Content workflow | Role |
| Workflow step roles | cms.contentworkflowsteprole | Content workflow step | Role |
| Workspace data permissions | cms.workspacedatapermission | Role | No regular object type. This object type, for a given workspace, connects a role to
application identifiers (which support being scoped under **Workspaces**) and workspace permission identifiers (defined in code when specifying the set of workspace permissions available for an application). |