Object types supported by continuous integration

Object typeCI folder nameNotes
Alternative formscms.alternativeform

Child object type with the following possible parent types: Custom tables, Forms, Page types 



Supported child objects:

  • States (cms.state)

CSS stylesheets



Only includes the definitions and settings of custom tables, not the data records stored within the tables.

Supported child objects:

Email templatescms.emailtemplate 



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 Continuous integration repository structure for more information.

Supported child objects:

Form controls

Meta filescms.metafile

Includes files related to other objects. For example thumbnail images of page types or email template attachments.

Page layouts (shared)cms.layout 
Page template categoriescms.pagetemplatecategory 
Page template scopescms.pagetemplatescopeChild object type of Page template objects.
Page templates


Supported child objects:

Page type scopescms.documenttypescope 
Page types


Supported child objects:

Queriescms.queryChild object type with the following possible parent types: Custom tables Page types
Settingscms.settingskeySettings are supported by continuous integration, but excluded by default in the repository.config file. Settings may contain sensitive data – only remove the exclusion if you agree to make all setting values available within the file system used by your application and any connected source control systems.
Statescms.stateChild object type of Country objects.
Transformationscms.transformationChild object type with the following possible parent types: Custom tables Page types
Web part categoriescms.webpartcategory 
Web part containerscms.webpartcontainer 
Web part layoutscms.webpartlayoutChild object type of Web part objects.

Web parts


Supported child objects:

Widget categories




Unsupported development objects

The following object types commonly used during development are currently NOT supported by continuous integration:

  • Custom modules - to synchronize module database objects across your development environment, use the export and import feature. To leave the modules open for editing after import, disable the Seal the selected modules option when selecting modules in the export wizard.
  • Resource strings - create and edit resource strings within resx files in the Kentico project. Use your source control system to synchronize the files between developers.

Page content

Object typeCI folder nameNotes
ACL items


Child object type of Page-level permission (ACL) objects.
Attachmentscms.attachmentChild object type of Page objects.
Categoriescms.categoryOnly includes global and site categories. User categories are not supported.

Page-level permissions (ACLs)


Supported child objects:

  • ACL items (cms.aclitem)



Only supported when not using workflow, as continuous integration is designed for use during the project's development phase.

The system uses multiple files to store page data. See the Pages section in Continuous integration repository structure for more information.

Supported child objects:

Page relationship typescms.relationshipname 

Page tags and tag groups

cms.taggroupTag groups are represented as a separate object type (cms.taggroup). Tags are stored within the data of individual Page (cms.document) objects.

Unsupported page permission scenario

Continuous integration does not support scenarios where different page-level permissions (ACLs) are applied to the same page from different sources and then synchronized.

Developer A

  1. Sets permissions for a user or a role on a page.
  2. Pushes the changes to the source control system.

Developer B

  1. Sets different permissions for the same user or role on the same page.
  2. Downloads the latest version from the source control. No collisions occur, because the ACL items are represented by different files.
  3. Restores objects from the file system to the database. Both ACL item files are processed, but only one is kept in the database, depending on the order in which they are processed.

On-line marketing

Object typeCI folder nameNotes

Activity types


Automation actions



Email campaign templatesnewsletter.emailtemplate 

MVT combinations


Child object type of Page template objects.
MVT variants om.mvtvariant Child object type of Page template objects.

Personalization variants

om.personalizationvariant Child object type of Page template objects.


Object typeCI folder nameNotes


Exchange tablesecommerce.exchangetable 
Order statusesecommerce.orderstatus 
Payment optionsecommerce.paymentoption 
Product internal statusesecommerce.internalstatus 

Product option categories


Supported child objects:

  • Product options (ecommerce.skuoption)
Product optionsecommerce.skuoptionChild object type of Product option category objects.
Product public statusesecommerce.publicstatus 
Product files ecommerce.skufile Child object type of Product objects.
Product variants ecommerce.skuvariant Child object type of Product objects.



Supported child objects:

  • Product files (ecommerce.skufile)
  • Product variants (ecommerce.skuvariant )
Shipping costs ecommerce.shippingcost Child object type of Shipping option objects.

Shipping options


Supported child objects:

  • Shipping costs (ecommerce.shippingcost)



Tax classes


Binding object types

In addition to the standard object types, continuous integration also supports most related bindings (i.e. objects representing relationships between the supported objects and other objects). For example, the binding objects that store how page templates or page types are assigned to sites.

BindingCI folder nameMain object type (parent)Related object type
Allowed child page typescms.allowedchildclassPage typePage type
Applications assigned to the default dashboard of rolescms.roleapplicationRoleUI element
Categories assigned to pagescms.documentcategoryPageCategory
Countries of tax classesecommerce.taxclasscountryTax classCountry
States of tax classesecommerce.taxclassstateTax classState
Device profile layouts of page templatescms.templatedevicelayoutPage templateDevice profile
Page layout (optional)
Exchange ratesecommerce.exchangerateExchange tableCurrency
Managers (users) of departmentsecommerce.userdepartmentUserDepartment
Mapped page layouts of device profilescms.deviceprofilelayoutDevice profilePage layout (source)
Page layout (target)
Page relationshipscms.relationshipPagePage
Page relationship type
Pages with fields containing other pages
(see Advanced content modeling)
Page relationship type
Payment options of shipping optionsecommerce.paymentshippingShipping optionPayment option
Permissions assigned to rolescms.rolepermissionRolePermission
Product bundlesecommerce.bundleProductProduct
Product options allowed for productsecommerce.skuallowedoptionProductProduct option
Product options of product variantsecommerce.variantoptionProduct variantProduct option
Product option categories of productsecommerce.skuoptioncategoryProductProduct option category
Roles assigned to formscms.formroleFormRole
Roles assigned to widgetscms.widgetroleRoleWidget
Roles in membershipscms.membershiproleMembershipRole
Scopes assigned to page typescms.documenttypescopeclassPage type scopePage type
Sites of CSS stylesheetscms.cssstylesheetsiteCSS stylesheetSite
Sites of data classescms.classsite

Page type
Custom table

Sites of page templatescms.pagetemplatesitePage templateSite
Sites of page relationship typescms.relationshipnamesitePage relationship typeSite
Sites of web part containerscms.webpartcontainersiteWeb part containerSite
Tax classes of departmentsecommerce.departmenttaxclassDepartmentTax class
Tax classes of productsecommerce.skutaxclassProductTax class
Tax classes of shipping optionsecommerce.shippingoptiontaxclassShipping optionTax class
UI elements allowed for roles (UI personalization)cms.roleuielementRoleUI element
Users in rolescms.userroleRoleUser