# Using Modular Content

Organizations often reuse previously approved content across many channels. With _Content Modules_, you can combine text, images, assets, and other data into groups that you can reuse in materials. You can also add new assets to _Content Modules_.

A _Content Module_ object record includes information such as the _Product_, _Country_, custom fields, and IDs. The _Content Module_ can also contain _Content Module Assets_, which provide links to the related document and object records. _Content Module Assets_ include:

* [Text Assets](/en/lr/57379/#claim-object), including _Claims_ and _Reusable Text Elements_ such as headers, titles, and other copy text
* Supporting component assets within the Vault Library
* Rulesets, collections of business _Rules_ that provide instructions on how to use _Content Module Assets_

## Creating Content Modules

You can manage _Content Modules_ in the _Modular Content_ tab. You can also navigate to **Business Admin > Objects > Content Modules** to create a _Content Module_. After creating a _Content Module_, you can create and add _Content Module Assets_. To add _Content Module Assets_, click the _Content Module_ to open the [_Content Module_](/en/lr/26387/) object record detail page. Then, enter <i class="far fa-pencil"></i> **Edit** mode and click **+ Claim**, **+ Image**, **+ Data**, **+ Text**, **+ Template**, or **+ Rules** to add the relevant asset types. You can search and filter for assets in the dialog.

To edit a _Content Module_ record's details, click <i class="far fa-external-link-alt"></i> to open the object record view and then click **Edit** to make changes. 

Once you populate a _Content Module_ with assets, you can reorder assets by clicking <i class="far fa-arrows-alt"></i> or dragging and dropping the cards. By default, you can add a maximum of 100 assets per _Content Module_. You can contact Veeva Support to raise this limit.

You can also click <i class="far fa-external-link-alt"></i> on an asset to view the _Content Module Asset_ record. Click the asset to open it in the Quick Look panel, which displays a thumbnail from the viewable rendition. You can edit _Content Module Asset_ fields while in the Quick Look panel. Vault displays <i class="fas fa-exclamation-circle" style="color: #ff0000;"></i> if a _Content Module Asset_ record includes incomplete required fields.

To remove an asset, click <i class="far fa-times-circle"></i>. When you're finished, click **Save** or **Save + Create**. You can re-enter _Edit_ mode by clicking <i class="far fa-pencil"></i> and selecting **Edit content** or **Edit details**.

<a href="https://platform.veevavault.help/assets/images/Content_Module_UI_24R12.png" data-lightbox="Content_Module_UI_24R12.png" data-title="" data-alt="Modular Content user interface">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/Content_Module_UI_24R12.png" alt="Modular Content user interface" style="width: 60%;"  />
</a>

Depending on how you manage your module library, you may want to include additional custom fields to help with organising and sorting, and include clear descriptions to make it easier for users to identify the correct modules within the library.

### Relating Content Modules

Using the join objects _Content Module Country_ and _Content Module Product_, you can relate _Content Modules_ to multiple products and countries. You can also relate modules using the [_Modular Content_ document panel][2].

You can optionally navigate to **Admin > Settings > Application Settings** and, under _Modular Content_, select the **Enable Content Module Country Join Object Record Creation SDK** and **Enable Content Module Product Join Object Record Creation SDK** checkboxes to enable automatic join record creation for the _Primary Country_ and _Primary Product_ values.

### Content Module Rulesets

Rulesets are collections of business _Rules_ that can be used across multiple _Content Modules_. To create a custom _Content Module Ruleset_, navigate to **Business Admin > Objects > Content Module Rulesets**.

### Creating Content Module Combinations

Using _Content Module Combinations_, you can group assets within _Content Modules_ for specific channels, messages, or personas.

To create a _Combination_ for a _Content Module_:

  1. Open a _Content Module_.
  2. Click <i class="far fa-plus-circle"></i> next to **Combinations** in the panel to the left of the module. 
  3. Enter a **Description**.
  4. Click **Continue**.

Once you create the _Combination_ record, you can begin adding _Assets_. By default, Vault selects all assets for inclusion. To manually select assets, clear the **Selected** checkbox and select any applicable assets. Click **Save** to finish editing the _Combination_. Vault creates _Combinations_ in the _Pending_ state. 

You can view _Combinations_ by opening the panel and clicking the _Combination_ name in the list. While viewing a _Combination_, you can click <i class="far fa-pencil-alt"></i> to edit the _Combination_ or <i class="far fa-trash-alt"></i> to delete the record. 

To open non- _Pending_ state _Combination_ records in a mini-browser window, click <i class="far fa-external-link-alt"></i>. From there, you can edit the record and move the _Combination_ through the _Content Module Combinations Lifecycle_. 

_Combinations_ are also used as a part of the [CRM Email builder](/en/lr/689127/).

### Making Local Copies

You can automate the generation of local _Content Modules_, allowing you to review and remove _Content Module Assets_ before generating a new copy. Vault supports local copies on the _Base_ and _Material_ types of the _Content Module_ object.

First, you'll need to download a controlled vocabulary configuration file and load it into your Vault using [Vault Loader](/en/lr/26607/). You can download the CSV file <a class="download-link " href="https://platform.veevavault.help/assets/downloads/Content_Modules_Reason_for_Copy.csv" target="_blank" rel="noopener">here<i class="fa fa-download" aria-hidden="true"></i></a>. Vault uses these records to automatically populate the _Reason for Copy_ field on _Text Asset_ records and _Content Modules_ generated using the _Make a Local Copy_ action.

Next, you must update [page layouts](/en/lr/26387/) for the _Text Asset_ and _Content Module_ objects to ensure Vault populates the _Reason for Copy_ field:

  1. Navigate to **Admin > Configuration > Objects > Text Asset > Layouts**.
  2. Click the **Claim Detail** page layout. 
  3. Click **Add** in the _Details_ section and select the **Reason for Copy** field.
  4. Click **Save**.
  5. Repeat steps 1 through 4 to add the **Reason for Copy** field to the **Reusable Text** object type page layout. You may first need to create the layout.
  6. Navigate to **Admin > Configuration > Objects > Content Module > Layouts**.
  7. Add the **Reason for Copy**, **Language**, and **Source Content Module** fields to the page layouts for all object types. You may first need to create the layouts.

Then, you must configure the **Make a Local Copy** user action:

  1. Navigate to **Admin > Configuration > Object Lifecycles > Content Module Lifecycle**.
  2. Click the state you want to configure the user action on.
  3. Under _User Actions_, click **Create**.
  4. Select **Always** and **Make a Local Copy**.
  5. Enter an **Action Label**.
  6. Click **Save**.
  7. Review [user permission sets][1] to ensure users can perform this action.

We recommend that you review your _Claims_ library for any records copied for localization purposes and add a _Reason for Copy_.

Once configured, you can perform the **Make a Local Copy** action on any _Content Module_. Next, you must select the target market values for **Primary Product**, **Primary Country**, and **Language** in the _Create local copy_ dialog.

Vault displays different information in the _Create local copy_ dialog depending on whether your Vault contains active _Content Module Country_ and _Content Module Product_ records:

  * If there are no active _Content Module Country_ or _Content Module Product_ records, the dialog includes prompts for _Primary Product, Primary Country_, and _Language_.
  * If there are active _Content Module Country_ records and no active _Content Module Product_ records, the dialog includes prompts for _Primary Product_, _Primary Country_, _Language_, and _Additional Countries_.
  * If there are no active _Content Module Country_ records and active _Content Module Product_ records, the dialog includes prompts for _Primary Product, Primary Country_, _Language_, and _Additional Product_.

_Primary Product_ and _Primary Country_ are required fields in all three dialogs.

On the _Make a Local Copy_ page, Vault provides different recommendations between the _Make a Local Copy_, _Use as is_, _Exclude_, and _Keep_ options depending on the asset type.

| Action | Behavior | Types |
| -- | -- | -- |
| Make a Local Copy | Vault creates a new record based on the original asset in the _Content Module_. <br> _Text Assets_ (_Claims_, _Reusable Text_): <br> &emsp; - _Source Text Asset_ field is populated based on the original _Text Asset_ <br> &emsp; - _Reason for Copy_ is populated as _Local Adaptation/Re-Use_ (UUID: 7862e62f-7dbe-49f8-8645-b233dfdc6927) <br> &emsp; - The created _Text Asset_ records include the _Primary Country_, _Primary Product_, and _Language_ values populated with the values from the _Create local copy_ dialog <br> &emsp; - Any _Additional Products_ or _Additional Countries_ entered are used to create the _Text Asset Country_ or _Text Asset Product_ records <br> _Documents_ (_Data_, _Image_): <br> &emsp; - Vault generates a new document based on the original document <br> &emsp; - _Country_, _Product_, and _Language_ values are populated based on the _Create local copy_ dialog <br> _Rules_: <br> &emsp; - Vault creates a new _Content Module Rule_ record | _Claims_ <br> _Reusable Text_ <br> _Data & Image Assets_ <br> _Rules_ |
| Use as is | Vault uses the existing _Asset_ in the new _Content Module_. | _Claims_ <br> _Reusable Text_ <br> _Data & Image Assets_ <br> _Rules_ |
| Exclude | Vault does not include the record in the local copy. | _Claims_ <br> _Reusable Text_ <br> _Data & Image Assets_ <br> _Rules_ |
| Keep | Vault keeps the _Content Module Combination_ record in the local copy. Newly created _Content Module Combination_ records respect actions performed on the assets. For example, if you mark an asset originally included in the _Content Module Combination_ as _Exclude_, Vault will exclude the asset. | _Content Module Combinations_ |

#### Recommendation Logic

When generating recommendations for _Claims_ and _Reusable Text_ records, Vault:

  * Checks the _Claims_ and/or _Reusable Text_ records in the original _Content Module_ for matches against the _Primary Country, Primary Product,_ and _Language_ values entered in the _Create local copy_ dialog]
  * Checks child records that meet the following conditions:
    * The _Source Text Asset_ field maps to a record on the original _Content Module_
    * The _Reason for Copy_ field value matches _Local Adaptation/Re-Use_ (UUID: 7862e62f-7dbe-49f8-8645-b233dfdc6927)
  * Considers all _Text Asset Country_ and _Text Asset Product_ records
  * Does not generate recommendations based on the _Language_ field if there is no _Language_ selected on the _Text Asset_ record
  * Provides one recommendation for all combinations of _Country_ and _Product_ selected

If Vault successfully matches the _Claims_ and _Reusable Text_ records, Vault recommends the **Use as is** action. If there are no matching _Claims_ and _Reusable Text_ records, Vault recommends the **Make a local copy** action.

When generating recommendations for _Data_ and _Image_ assets, Vault considers the _Rights Country_ and _Rights Language_ fields. If the _Rights Country_ and _Rights Language_ field values match your selections in the _Create local copy_ dialog, Vault recommends the **Use as is** action. If there is no match, Vault recommends the **Exclude** action.

When generating recommendations for _Content Module Rules_, Vault always recommends **Use as is**.

When generating recommendations for _Content Module Combinations_, Vault always recommends **Keep**.

## Previewing Base & Material Content Modules

While viewing a _Content Module_ with the _Base_ or _Material_ type, you can perform the **Generate Preview** action, allowing you to generate HTML _Content Module_ previews in PromoMats by combining the module and an HTML _Template_. 

The _Generate Preview_ action is available on all states of the _Content Module_ object lifecycle. By default, [Atomic Security](/en/lr/47850/#Atomic_Security_Actions) allows all Vault users to execute this action. You can perform this action from the record in **Business Admin** by clicking the **Actions** menu or from a module in the _Modular Content_ tab by clicking **Generate Preview**. You can also generate previews for a _Content Module Combination_ by opening a record and clicking **Generate Preview**.

Once you generate a preview link on an _Active_ record, you can also click **Show Preview** to re-open the preview if the previously generated preview is still valid. Vault displays a notification when the preview link is ready. Vault generates a maximum of 20 previews per _Content Module_ or _Content Module Combination_. Preview links are user-specific and cannot be shared. Previews are valid for 24 hours.

When generating a preview, you must first add at least one _Template_ to the _Content Module_. 

<a href="https://platform.veevavault.help/assets/images/Content_Module_HTML_Preview_24R3.png" data-lightbox="Content_Module_HTML_Preview_24R3.png" data-title="" data-alt="Content Module">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/Content_Module_HTML_Preview_24R3.png" alt="Content Module" style="width: 60%;"  />
</a>

### Managing Groupings

Groupings indicate how or where a _Content Module Asset_ is used and serve as a filter to easily locate _Assets_ within the _Content Module_ object record detail page. You can assign a grouping to an _Asset_ by entering <i class="far fa-pencil"></i> **Edit** mode, opening the **Quick Look** panel of the _Asset_, and selecting the desired value from the **Grouping** picklist.

You can also [manage this picklist](/en/lr/1269/) by navigating to **Business Admin > Picklists > Content Module Asset Grouping**.

### Adding HTML Templates

To add a _Template_ asset to a _Content Module_, click **+ Template**. _Templates_ can be any document type, but they must be a .html, .htm, or .xhtml file. Vault automatically applies filters on the _Product_ and _Country_ fields in the _Select Template_ dialog.

You can also add multiple _Templates_ and select which one Vault uses to generate the preview when performing the _Generate Preview_ action.

Download a sample .html _Template_ <a class="download-link " href="https://platform.veevavault.help/assets/downloads/Sample_HTML_Template_24R3.html" target="_blank" rel="noopener">here<i class="fa fa-download" aria-hidden="true"></i></a>. This _Template_ uses a _Claim_ asset with grouping value of header, an _Image_ asset, and an additional _Claim_ asset tagged as a footer.

### Using Vault Tokens for HTML Previews

You must include Vault tokens within your HTML _Templates_ before generating an HTML preview. These tokens specify the _Content Module Asset Type_ to use, the [Rendition Type](/en/lr/3037/) (for document assets), and the specific grouping.

The token format for HTML _Templates_ is `{{ContentModuleAssettype.objecttype__v;rendition.rendition_type;grouping.grouping_type}}`. At a minimum, the token must specify the _Content Module Asset Type_, whose format is `{{ContentModuleAssettype.objecttype__v;}}`, while the rest is optional. You can only include one grouping per token. For example, a _Claim_ used with a header grouping would be `{{ContentModuleAssetType.claim__v;grouping.veeva_header__v;}}`. Each token added to the HTML _Template_ must be unique.

Before generating a preview, Vault validates against the following parameters:

| Issue | Expected Error Message |
| --- | --- |
| The template has no `{{ContentModuleAssetType.objecttype__v;}}` tokens. | Selected document is not supported. _Template_ does not include asset tokens. |
| A referenced `objecttype` in a token is invalid. Unsupported object types: <br> &emsp; - Custom types (`__c`) <br> &emsp; - `rules__v` <br> &emsp; - `template__v` | Referenced object type in token is invalid. |
| Token contains an unsupported key, including typos. | Referenced token is invalid. Unsupported keys entered. |
| Multiple keys entered in a token. | Referenced token is invalid. Duplicate keys are unsupported. |
| A rendition is specified for `claim__v` or `text__v` token. | Referenced token is invalid. Rendition cannot be specified for `claim__v` or `text__v` tokens. |
| The template uses more than the maximum number of `image__v` and `data__v` tokens (10). | The maximum limit of 10 tokens for image/data types has been exceeded. Please reduce the number of tokens for images/data types. |
| The template uses more than the maximum number of `claim__v` and `text__v` (20).  | The maximum limit of 20 tokens for claims/reusable text types has been exceeded. Please reduce the number of tokens for images/data types. |
| The template uses duplicate tokens. | Duplicate tokens detected. Please ensure each token is unique and try again. |

Vault supports the following file types for `image__v`/`data__v` tokens:

  * SVG (.svg)
  * WebP (.webp)
  * HEIF/HEIC (.heif, .heic)
  * TIFF (.tif, .tiff)
  * JPEG (.jpg, .jpeg)
  * PNG (.png)
  * GIF (.gif)

Image files must be smaller than 20MB.

### Generating CRM Email Module Previews

You can also use the [CRM Email Builder](/en/lr/689127/) to build and preview _CRM Email_ modules. 

## Reviewing & Approving Content Modules

When you've finished creating your _Content Module_, you can send the module for approval through the _Content Module Approval_ workflow. To send the module for approval, click the **Actions** menu, select **Start Approval**, and assign users as **Content Module Reviewer** and **Editor**. Once the module is approved, you can begin using it in your materials.

### Commenting on Content Modules

You can comment on _Content Modules_, _Content Module Assets_, and _Combinations_. To open the **Comments** panel, click <i class="far fa-comment"></i>. Vault displays <i class="far fa-comment"></i> with an orange notification dot if there are unresolved comments. You can click a _Content Module Asset_ comment to highlight the corresponding card and quickly understand which asset the comment is for.

Vault displays <i class="fas fa-comment-exclamation" style="color: #cc6600;"></i> on a _Content Module Asset_ card if there are unresolved comments for that specific asset. You can click the icon to view that asset's comments in the comments panel, or you can click the card to view the comments in the Quick Look panel. You can add comments to _Content Modules_ or _Combinations_ from the comments panel. You can add comments to _Content Module Assets_ on the Quick Look panel. In the Quick Look panel, click **All Comments** to switch to the **Comments** panel.

By default, Vault only displays _Unresolved_ comments. Click <i class="far fa-filter"></i> to view **All** comments or only **Resolved** comments. You can also hover on a comment and click the **Actions** menu to **Reply**, **Resolve**, **Edit**, or **Delete** it. You can only edit and delete your own comments and replies. Vault Owners can delete any comments. You can resolve and reopen any comments.

Vault displays <i class="fas fa-comment-check" style="color: #539138;"></i> on _Resolved_ comments. Click the icon to reopen the comment.

If you want to notify a user about a comment, mention them by typing "@" and the beginning of their first name, last name, or Vault username in the _Comment_ field and selecting from the list of users. 

<a href="https://platform.veevavault.help/assets/images/Generate_Preview_Modular_Content_24R32.png" data-lightbox="Generate_Preview_Modular_Content_24R32.png" data-title="" data-alt="Content Module record">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/Generate_Preview_Modular_Content_24R32.png" alt="Content Module record" style="width: 60%;"  />
</a>

#### Limitations

The following limitations apply to comments on _Content Modules_:

  * You cannot add more than 5,000 comments per _Content Module_.
  * You can only add new comments while in _View_ mode.
  * When delegates add comments, Vault displays their name rather than the delegate user's name.
  * You can add a maximum of 50 user mentions to an individual comment or reply.

##  Using the Modular Content Panel {#panel}

The _Modular Content_ [document panel](/en/lr/9753/#doc-info-panels) displays _Content Modules_ of the _Material_ type related to a document, including _Content Module Assets_ and _Content Module Combinations_. The panel lets users link _Content Module Assets_ to specific elements within the document and add or remove _Content Module Combinations_ to _Content Modules_ for display. Click <i class="far fa-cubes"></i> to open the Modular Content document panel, and click <i class="far fa-filter"></i> to apply a **Filter**. You can also navigate the _Modular Content_ panel using the **Tab** key.

<a href="https://platform.veevavault.help/assets/images/25r3.2-promomats-modular-content-panel.png" data-lightbox="25r3.2-promomats-modular-content-panel.png" data-title="" data-alt="Modular Content document panel">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/25r3.2-promomats-modular-content-panel.png" alt="Modular Content document panel" style="width: 60%;"  />
</a>

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Vault only displays the <em>Modular Content</em> panel on documents using the <em>Source Content Module</em> field.</p>
    </div>
  </div>
</div>



### Adding & Viewing Content Modules

The panel displays _Content Modules_ added during document creation and those added manually. Click <i class="far fa-filter"></i> to show or hide linked and unlinked _Assets_.

To add _Content Modules_ manually, click the **plus** (**+**) icon in the _Modular Content_ panel.

You can also identify _Content Modules_ when first uploading a document to Vault by selecting the modules in the _Source Content Module_ field.

Vault displays active links in blue text and inactive links in gray. You can hover over an active module or asset link to view the hovercard. Vault displays document-linked _Content Module Assets_ with the thumbnail of the document in the hovercard. Clicking an active link opens [_Annotate_ mode](/en/lr/9753/#annotate) and jumps to the link's location in the document. 

Click <i class="far fa-external-link"></i> next to a _Content Module_ or _Content Module Asset_ within the panel to open the associated record in a mini-viewer window or the document in a new tab.

You can use _Link Annotations_ to manually link to _Content Module Assets_ within the _Modular Content_ document info panel or automatically using the Auto-Linking functionality for _Text Assets_. If you create a link annotation to either a _Text Asset_ or a _Content Module Asset_ document, Vault displays the asset as an active link in the panel. Click the asset to navigate to the annotation within the document.

When an asset is marked as _Must Use_ on the _Content Module_ record, Vault displays <img class="inline" src="https://platform.veevavault.help/assets/images/Modular_Content_Must_Use_Icon_25r23.png" alt="Must Use icon" style="" /> next to the asset in the panel. 

When a _Content Module Asset_ is linked to multiple matches, Vault displays a square number icon next to the asset in the _Modular Content_ panel. The icon represents the number of annotations linked to the asset to a maximum of five. You can click the asset link or the icon to open _Annotate_ mode and view the asset matches.

Vault displays the <i class="fal fa-lightbulb"></i> icon when a _Content Module Asset_ is linked to a pending Suggested Link annotation. You can click the asset link or icon to enter _Annotate_ mode and navigate to the pending Suggested Link annotation. Accepting the Suggested Link annotation removes the icon next to the _Content Module Asset_. If you reject the Suggested Link annotation, Vault removes the icon and displays an inactive asset link. 

If a _Content Module Asset_ is linked to multiple annotations and at least one annotation is a pending Suggested Link, Vault displays the <i class="fas fa-exclamation-triangle"></i> icon. You can click the icon or the _Content Module Asset_ to open a modal and enter _Annotate_ mode. From there, you can navigate to the annotations. Accepting the pending Suggested Link converts the icon to the standard multiple link icon upon refresh. You can view up to five asset matches. Rejecting the Suggested Link annotation will convert the icon to a multiple icon upon refresh.

### Adding & Viewing Content Module Combinations

The panel also can display _Content Module Combinations_ added to _Content Modules_.

To add a _Content Module Combination_, click the **plus** (**+**) icon next to each Content Module in the _Modular Content_ panel. Then, you can search for and select from existing _Content Module Combinations_ in the search dialog to add or remove combinations from a _Content Module_. Vault filters the list by default to display only the _Content Module Combinations_ available for the associated _Content Module_.

Once you add a _Content Module Combination_, Vault also automatically adds the name of the combination to the _Content Module Combination_ document field available in the _Information_ section. You can also update the combination in this document field from _Edit_ mode in the _Information_ section. To enable this document field, ensure that the _Content Module Combination_ document field is active and added to the _Document Type_ of the document. Updating the document field in the _Information_ section also adds the combination to the associated _Content Module_ in the _Modular Content_ panel.

You can expand a _Content Module_ to review the associated _Content Module Combination_ and the _Content Module Assets_ listed in the combination. If you hover over the name of the _Content Module Combination_, Vault displays a hovercard with the details of the combination. Hovering to the right of the combination displays a link that opens the _Content Module_ record in a mini-viewer window with the combination selected by default. 

Vault also displays _Content Module Assets_ active links in blue text and inactive links in gray under the expanded _Content Module Combination_. You can hover over an active asset link to view the hovercard. Vault displays document-linked assets with the thumbnail of the document in the hovercard. Clicking an active link opens licking an active link opens [_Annotate_ mode](/en/lr/9753/#annotate) and jumps to the link's location in the document.

### Adding Asset Links

If Vault cannot identify an _Asset_, you can click <i class="far fa-comment-alt-plus"></i> to manually add a link to a document or _Text Asset_, then select an area on the document to create a manual link annotation to the _Text Asset_ or document identified in the _Content Module Asset_. You can also add a link to an image asset. The link type depends on the _Content Module Asset Type_. 

### Rules

_Content Module Rulesets_ are grouped with other _Content Module Assets_ in the _Modular Content_ panel. Unlike other assets, you cannot link _Rulesets_ to anything within the document. 

## Downloading Content Modules

In the _Modular Content_ document panel, click <i class="far fa-download"></i> to download _Content Modules_ in a ZIP file. You can also enable the **Download Content Modules** action on one or more states in the _Content Module Lifecycle_ and perform this action on individual _Content Module_ records. You may need to update _Content Module_ object permissions to allow users to download individual _Content Module_ records. Vault notifies you when the _Content Modules_ are available to download. The process may take several minutes to complete.

When you download _Content Modules_, Vault generates a read-only Excel file containing the _Content Module_ manifest. Each _Content Module_ in the export has its own tab in the spreadsheet. These tabs contain all standard and system-managed fields on the _Content Modules_, such as _Products_, _Countries_, and _Content Module Assets_.

You cannot download _Content Modules_ if the total ZIP file size exceeds 100 GB in size.

If you do not have the [correct permissions][1] to view _Content Modules_ and _Content Module Assets_, you cannot view the downloaded files or the contents of the manifest. 

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: When you download <em>Content Modules</em>, Vault does not include <em>Content Module Combinations</em>.</p>
    </div>
  </div>
</div>



##  Related Permissions {#permissions}

You must have the _Annotate_ document role permission to create annotations. To create link annotations, you also need the _Edit Relationships_ document role permission.

You must have the _Object: Content Module: Read_ and _Object: Content Module Asset: Read_ permissions to view module and asset records. To download _Content Modules_, you must have these permissions along with _Object: Text Assets: Read_, _Object: Content Module Rulesets: Read_, and _Object: Ruleset Rules: Read_. You must also have _View Document_, _View Content_, and _Download Source_ permissions on documents linked within image and data _Content Module Asset Types_.

You must have the _Object: Content Module Combination: Create_, _Edit_ and _Object: Content Module Asset Combination: Create_, _Edit_ permissions to create _Content Module Combinations_.

You must configure [**Atomic Security**](/en/lr/47850/) for _Read_ and _Edit_ permissions on the _Content Module Lifecycle_ state for the _Content Module and Text Asset Comments_ object. You must also have the _Object: Content Module and Text Asset Comments: Read, Create, Edit, Delete_ as well as _Object: Content Module and Text Asset Replies: Read, Create, Edit, Delete_ permissions to comment on the _Content Module_.

When creating local copies, Vault only checks permissions for the record types included in the _Content Module_. For example, if the module does not include _Content Module Combination_ records, the _Object: Content Module Combination: Create, Read_ permissions are not required.

You must have the following permissions on the applicable object types, records, and documents to create local copies of _Content Modules_:

  * _Object: Content Module: Create_, _Read_
  * _Object: Content Module Asset: Create_, _Read_
  * _Object: Text Asset: Create, Read_
  * _Object: Content Module Combination: Create, Read_
  * _Object: Content Module Asset Combination: Create, Read_
  * _Object: Match Text Variation: Create, Read_
  * _Object: Text Asset Country: Create, Read_
  * _Object: Text Asset Product: Create, Read_
  * _Document Role: View, Create Document_
  * _Read_ on the _Name_, _Description_, _Primary Country_, _Primary Product_, and _Language_ fields on the _Content Module_ object
  * _Read_ on the _Name, Lifecycle State_, _Match Text, Must Use,_ and _Grouping_ fields on the _Content Module Asset_ object
  * _Read_ on the _Content Module_, _Name_, _Lifecycle State_, and _Description_ fields on the _Content Module Combination_ object
  * _Read_ on the _Content Module_, _Content Module Asset_, and _Content Module Combination_ fields on the _Content Module Asset Combination_ object


 [1]: #permissions
 [2]: #panel