Overview
If your business serves global users, you may want to ensure you can communicate with them according to their preferred language. While translations of system-generated texts are provided for all languages supported in the GAN Integrity platform, many forms and areas of the UI are configured to meet the specific needs of your business. For these configured texts, the translations need to be provided to the platform via a CSV file upload.
These translations can be managed via the System Administration space:
Enabling Translations
The System Administration space (including the Translations option) is available for all users designated as administrators.
For information on granting the admin role, see the Administrator Role & Workspace documentation.
Managing Translations
If you have access to the System Administration space, you will see a module / application menu for navigation, from which translation functionality can be accessed.
Click any module to open the Translations editor for that application:
Below we will break down the UI piece by piece, starting from the bottom, as downloading a file will typically be the first action you will need to take.
Downloading Translations & Previewing Forms
NOTE: Translation file imports require a specific format and the import process will fail if the file is not in the correct format. The best way to ensure that you have the correct format (and will have a successful upload) is to first download a file, follow the instructions in it, and then upload that.
You have the option to download all form / UI content for the module / application:
Or you can download for a single form:
For form-specific downloads, select the relevant record type, then choose the applicable form:
Note that you have a preview option to help ensure that you are selecting the correct form. This also provides an opportunity to validate the translated data following an upload, as you can select the language in which to view the form.
Whether you select to export a single form, or all forms for a module, the translation download typically happens within a few seconds. If you wait in the UI for it, it will download automatically. However, you are welcome to navigate away to complete other work, and can then download the file from the Notification Center later.
Working with Translation files
Translation files require a specific format to be able to be read and processed by the system. The best way to ensure you have the correct format is to start with an export, and follow the instructions provided in the top row of the file.
Specifically, only the highlighted columns in the screenshot below should be edited in any way, and all headers must be left as they appear in the export.
The initial fields provide a mapping of the data point and how it is used in the configuration, followed by the text provided in the default language (which cannot be edited via a translation import).
Enter the translated content in the relevant fields, save the file, and import it when ready.
Importing Translations
To import a translation file, simply select the relevant module / application, and load the file.
The time the file takes to load will vary depending on the amount of content, number of translations, etc. Many loads will complete within a few seconds, while others will take longer. While the file loads, you will see information that it is uploading if you stay within the page, but you are welcome to navigate away and can check on it later via the Notification Center.
Translation processes can have the following statuses:
Done: The process completed successfully
Failed: The process was unable to complete
In all cases, clicking on the notification card will navigate you to a page with additional information, including error information in the case of a process failure.
Working with Multiple Import Files
You may find it necessary to split translations across multiple files — for example, if you're translating a large export in batches, or handling different languages separately. The following behavior applies when importing multiple files.
Additive imports (no overlap): If your first file contains rows 1–500 and your second file contains rows 501–1000, the two imports will add to each other. Existing translations are preserved and no data will be overwritten, since neither file touches the same rows.
-
Overlapping imports (rows or columns present in multiple files): This applies in two common scenarios:
Rows: If your first import contains translations for rows 1–500, and your second import includes those same rows but with the translation fields left blank, the existing translations for rows 1–500 will be removed.
Language columns: If your first import fills in Spanish translations across all rows, and your second import fills in French translations but leaves the Spanish column blank, the Spanish translations will be removed.
NOTE: Importing a row or column with blank values will remove existing translations for that row or column, reverting those fields to the default language.
To avoid unintentionally removing translations:
Only include rows you want to update — delete any rows from the file that you are not actively translating.
Only include language columns you want to update — delete any language columns from the file that you are not actively translating.
Alternatively, use the form-specific download option to export a smaller, targeted file rather than working from a full export with partial content.
History & Auditing
The Translations History allows you to access previously downloaded and uploaded files.
Click the button to open the history where you can access previously handled files, alongside information about who accessed or provided the file and when, as well as to see errors for any failed processes.
Note that the history can act as an un-do option if needed, in that you can download a previously downloaded or uploaded file and re-load it. In addition, this supports troubleshooting as you can see any errors that happened during upload via the “View Report” option.
However, simply downloading or uploading a file does not necessarily imply that the configuration or translation has been changed, as a download has no impact, and an upload could fail and not actually lead to a data change.
Therefore, when actual changes occur as a result of translation processes, they are logged in the overall System Administration history, along with other changes applied within the System Administration space.
For easy navigation, you can filter by date, type of change, or application / module.
Need more help? Please contact your Customer Success Manager for general guidance or our Support Team for troubleshooting assistance.
© 2026 GAN INTEGRITY INC. ALL RIGHTS RESERVED | The information contained in this document is solely for the intended recipient and may not be used, published or redistributed without the prior written consent of GAN INTEGRITY INC. While every care has been taken in preparing this document, GAN INTEGRITY INC. reserves the right to revise its contents without prior notice.