# Configuring Engage Integration

Vault automatically creates most of the configuration elements that you need to use the feature. This article explains the additional steps you'll need to complete and provides information on some of the configurations that are automatically provided.

## Configuration Steps

To use Engage Integration, an Admin (with a security profile that grants the right access) must complete these configurations:

  * **Create object data records**: [Create data records](/en/lr/18769/) for the [_Product_](/en/lr/25318/), [_Key Message_](/en/lr/18656/#objects), and [_Website_](/en/lr/18656/#objects) objects. These records correspond to entities in CRM, so you must verify that the object fields used to match records between Vault and CRM are correct.
  * **Set up manual send actions**: Vault automatically sends documents to Engage when they meet the necessary criteria. You may need to configure additional user actions that allow users to manually push a document if the automatic send fails. The default _CRM Content Lifecycle_ already includes user actions for some states.
  * **Set up lifecycle state send actions**: Configure lifecycle state entry actions that send a document to Engage. Vault automatically sends _Multichannel Slide_ documents when the distribution package or certain metadata change, but does not automatically send when the document changes states. To ensure that approved content is sent to the production environment, we recommend that you set up this entry action on the _Steady_ state.
  * **Set up withdraw actions**: [Configure lifecycle state entry actions](/en/lr/12399/) that automatically withdraw documents from Engage. By default, the _CRM Content Lifecycle_ withdraws documents as an entry action for the _Expired_ state, but this is important if you use a custom lifecycle or custom states. For withdrawal, you must specify the environment. Vault automatically makes **Withdraw from Stage Engage** and **Withdraw from Production Engage** user actions available once a document version is published, so you do not need to configure those actions. Entry actions ensure that old versions are removed, even if users forget to do so manually.

## Associated Configuration Options

The following are available in your Vault:

  * **Document Types**: Users can apply the _Multichannel Slide_ and _Multichannel Presentation_ document types to content that will be sent to CLM.
  * **Document Fields**: Engage Integration includes a robust set of [document fields](/en/lr/18152/#fields) that control the options on a document once it's published through Engage.
  * **Vault Objects**: The _Website_ and _Key Message_ objects hold metadata that corresponds to records in Engage. The _Distribution_ object tracks send to Engage actions for documents. Vault automatically creates _Distribution_ object records and uses them to store details like where and when a particular document was sent, as well as error messages when auto-sending fails. The _CRM Message Template_ object holds approved messages that CRM users can select when sharing content as web links.
  * **Rendition Types**: To successfully publish presentations and slides, a document must have a distribution package in a format appropriate to Engage. For this, users have various distribution [package rendition types](/en/lr/25892/).
  * **Distribution to China**: If your organization distributes content to Chinese customers, you can enable the shared document field [_Use China CDN_](/en/lr/63412/) which can be used to indicate that Vault should replicate the content to the China-hosted CDN.
  * **Lifecycle**: Vault automatically creates the _CRM Content Lifecycle_. You can choose to use this lifecycle or another for _Multichannel Slide_ documents.
  * **User Actions for Sending**: Vault automatically adds the _Send to Engage_ user actions to _CRM Content Lifecycle_ states, but you can also configure this action for other lifecycles. Because the feature automatically sends content, manual user actions serve to allow re-sending in case of errors during the automatic send.
  * **User Actions for Creating Presentations**: Add the **Create Presentation** user action to any lifecycle states from which users should be able to [auto-generate a presentation](/en/lr/28786/#generate).
  * **User Actions for Obsolete State Types:** Initiate the _Obsolete related presentation and slides_ user action to automatically move _Multichannel Slides_ and _Multichannel_ _Presentations_ to their lifecycle's obsolete state when the document they were generated from moves to an obsolete state. The _Obsolete_ _dropped slides_ user action moves _Multichannel Slides_ removed from a _Multichannel_ presentation to their lifecycle's obsolete state.

## Website & Key Message Objects {#objects}

The _Website_ object allows users to specify a site where Vault should publish the Engage content.

## Product Mapping

When using Engage Integration, it's important that [products are set up properly](/en/lr/25318/) in both Vault and CRM.