**Source URL:** https://platform.veevavault.help/en/lr/11847442/

# Configuring Document Translation

Users can translate documents directly within Vault. To make this functionality available to users, Admins must authorize, configure, and activate the DeepL translation provider connection, the Google Cloud Translate translation provider connection, or both connections, and then configure document translation user actions on the appropriate document lifecycle states.

## Configuration Overview

To configure document translation, you must:

* Have an account and API key with the DeepL Translation or Google Cloud Translation service.  
* Configure and activate the translation provider [_Connection_][2] record.
* Optional: Use MDL to configure the translation document [relationship type and document fields][3] copied during translation.  
* Configure the [user actions][4] on the necessary document lifecycle states.

## Configuring & Activating the Connection {#configure-connection}

After adding the _API Key_ to the appropriate _Connection Authorization_ records, you must configure and activate the associated _Connection_ record. When activating the connection, Vault syncs which languages are available for document translation using the translation provider's available languages and Vault's languages (in **Admin > Settings > Language & Region Settings**).

When users translate documents using the Google Cloud Translate translation provider, documents are limited to 40MB, unless you configure a _Storage Location_ for the Google Cloud Storage bucket used for staging file translation uploads. Documents translated with the DeepL translation provider do not have a file size limit.

To configure the DeepL or Google Cloud Translate connection:

1. Navigate to **Admin > Connections > Connections**.  
2. Open the **DeepL** or **Google Cloud Translate** _Connection_ record.  
3. Verify that the **URL** is correct for your configuration. To change the **URL**, click **Edit** (), update the **URL** as needed, and click **Save**.
4. Optional: If configuring the DeepL connection:  
   1. Click the **DeepL** record in the **Translation Provider Config** field to open the DeepL _Translation Provider Configuration_ record.  
   2. Click **Edit** ().  
   3. Enter the **Glossary ID** for the translation glossary you want to use.
   4. Enter the **Translation Memory ID** for the translation memory you want to use.  
   5. Click **Save**.  
5. Optional: If configuring the Google Cloud Translate connection:  
   1. Click the **Google Cloud Translate** record in the **Translation Provider Config** field to open the Google Cloud Translate _Translation Provider Configuration_ record.  
   2. Click **Edit** ().  
   3. Enter the **Glossary ID** for the translation glossary you want to use.  
   4. Enter the **Storage Location** for staging file translation uploads.  
   5. Click **Save**.  
6. Return to the _Connection_ record and click **Edit** ().  
7. From the **Authorization** field drop-down, select **Create Connection Authorization**.  
8. In the _Create Connection Authorization_ dialog, select **API Key** and click **Continue**.  
9. Enter the **Name** of the API Key _Connection Authorization_ record and click **Save**.  
10. Click **Save** on the _Connection_ record.  
11. In the **Authorization** field, click the **Connection Authorization** record you just created.  
12. Select **All Actions > Set API Key**.  
13. In the _Set API Key_ dialog, enter your DeepL API key or Google Cloud Translate service account key in the **API Key** field and click **Save**.  
14. Return to the _Connection_ record.  
15. Select **All Actions > Sync Supported Translation Languages**. Vault updates the available translation languages and sets the record's _Lifecycle State_ to _Active_.

**Important**: If you update the _Translation Provider Configuration_ record any time after initial configuration, select **All Actions > Sync Supported Translation Languages** on the associated _Connection_ record to update the configuration.

## Configuring the Translation Relationship & Copied Document Fields {#configure-translation-relationship}

**Note**: These configuration steps are optional.

By default in most Vaults, when a document is translated, Vault creates a _Translation_ relationship on the source document and _Translation Of_ relationship on the translated target document to link the two documents. You can use MDL to change the relationship type created between the two documents during translation.

By default, when translating a document, Vault copies all document fields from the source document to the target document. You can use MDL to configure which fields are copied to the target document during translation.

## Configuring User Actions {#configure-user-actions}

Configure the _Translate Document with DeepL_ or _Translate Document with Google Cloud Translate_ user action on each document lifecycle state for which you want users to initiate document translation. After adding these user actions to a document lifecycle state, Vault applies the _Execute_ Atomic Security permission for these user actions to the default document role on the document lifecycle state. You can update the Atomic Security for the user actions as needed.

To configure user actions:

1. Navigate to **Admin > Configuration > Document Lifecycles > [Lifecycle] > States > [State] > User Actions** and click **Create**.  
2. Click **Create Rule** to add a new user action.  
3. From the **Condition Type** drop-down, select **Always**.  
4. From the **Allow the following actions** drop-down, select **Translate Document with DeepL** or **Translate Document with Google Cloud Translate**.  
5. Optional: Change the **Action Label** as needed.  
6. Click **Save**.

Repeat the above steps to add translation user actions to any additional document lifecycle states.

## Limitations

By default, the Google Cloud Translate service allows translation for documents up to 40MB. To translate documents over 40MB with Google Cloud Translate, configure a [Google Cloud Storage Location][2].

## Related Permissions

The _Vault Owner_ and _System Administrator_ security profiles include all permissions needed to configure document translation. For other security profiles, the following permissions are required:

| Type | Permission Label | Controls |
| ----- | ----- | ----- |
| Security Profile | Admin: Document Lifecycles | Grants the ability to configure document translation user actions on document lifecycle states. |
| Security Profile | Application: Connections: Manage Connections | Grants the ability to view and manage connections in the _Connections_ tab in Vault Admin. |
| Security Profile | Objects: Connection, Connection Authorization, Connection Client, and Translation Provider Config: Edit | Grants the ability to edit _Connection_, _Connection Authorization_, _Connection Client_, and _Translation Provider Config_ records. |

[2]: #configure-connection
[3]: #configure-translation-relationship
[4]: #configure-user-actions