---
sourceDocument: Brazil Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/governance-risk-compliance

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Translate external PDR form fields

# Translate external-facing Personal Data Rights form labels and values {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Add translation values for the configurable fields on the external-facing Personal Data Rights (PDR) form, so that text specific to your organization is correctly translated.

## Before you begin

Install the language plugins for the languages you want to support. For a list of available plugins and steps to activate one, see [Activate a language](https://www.servicenow.com/docs/access?context=t_ActivateALanguage&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).

Verify that an active external form configuration record exists. For steps, see [Create a PDR external-facing form configuration record](https://www.servicenow.com/docs/T9av6XaWpE9Mog3lnocC6g "Create the parent external form configuration record that anchors all location, data subject type, and request type rules for the external-facing Personal Data Rights (PDR) form.").

Role required: sn_grc_pdr.pdr_admin

## About this task

The external-facing PDR form supports multiple languages. Most static field labels such as Description or Request submitted by, are hardcoded strings that are translated
automatically when the corresponding language plugin is installed.

However, content that you enter manually on the external form configuration record is specific to your organization, so the system doesn't translate it automatically. These include the form title, sub-title, introduction, and
guidance text that appear at different stages of the form. To provide your own translations for a field, you must create a new record in the Translated Text \[sys_translated_text\] table and add the translated text for these
fields.

## Procedure

1. Navigate to AllSystem LocalizationTranslated Text.
2. To add a new translation, select New.
3. On the form, fill in the fields.  
   {#translate-pdr-form-text__entry__2}

   | Field | Description |
   |-|-|
   | Table Name | Configuration table that hosts the field you want to translate. Note: The options in Field Name depend on the table you select. For example, if you want to translate the title, sub-title, or guidance text in the form, select PDR external facing form configuration. If you want to translate the introductory text for a jurisdiction, select PDR external facing form location config. |
   | Document | Parent external form configuration record that is currently active in your instance. |
   | Field Name | Field whose text you want translated in the external-facing form. Create separate translation records for each field you want to translate. |
   | Language | Language that the field value is translated into. If you want the same field translated to other languages, you must create separate translation records for each language. |
   | Value | Translated text that appears on the external form for the selected field. |
   [ ]

4. Select Submit.

## Result

When a requester selects the translated language on the external-facing PDR form, the form displays the translated value.
**Related topics**   

* [Translating individual UI strings](https://www.servicenow.com/docs/access?context=c_TranslateIndFieldLabelsAndValues&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US)
* [Translated text table](https://www.servicenow.com/docs/access?context=r_TranslatedText&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US)

*[\>]: and then