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:

Configuring & Activating the 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.

Configuring the Translation Relationship & Copied Document Fields

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 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.

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.