--- schema_version: "1" id: 325887c17416dc5d4e4e4729743c9a8acb15db00b035fc42aea79673b3eec290 title: Nonprofit Success Pack and Translation collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/npsp_and_translation.md canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.npsp_and_translation.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: f9bec20a3457626f2e06ab9f7c466db184de3d7ca1d56abb7047bbf70d746601 description: This document provides a list of areas in the Nonprofit Success Pack that cannot or should not be translated. products: - Nonprofit release: "264" --- # Nonprofit Success Pack and Translation This document provides a list of areas in the Nonprofit Success Pack that cannot or should not be translated. - **[Frequently Asked Questions](https://help.salesforce.com/s/articleView?id=sfdo.npsp_and_translation.htm&release=264.0.0&type=5)** Get answers to questions about localization, including frequency, languages, and documentation. - **[Available Languages](https://help.salesforce.com/s/articleView?id=sfdo.npsp_and_translation.htm&release=264.0.0&type=5)** See the list of languages available for NPSP. - **[Localized Documentation](https://help.salesforce.com/s/articleView?id=sfdo.npsp_and_translation.htm&release=264.0.0&type=5)** Get links to documentation in other languages. - **[Enable Languages](https://help.salesforce.com/s/articleView?id=sfdo.npsp_and_translation.htm&release=264.0.0&type=5)** Enable localization in Salesforce for your NPSP product. - **[Translation Limitations](https://help.salesforce.com/s/articleView?id=sfdo.npsp_and_translation.htm&release=264.0.0&type=5)** If you're localizing your org on your own, keep in mind that there are some issues and considerations due to the nature of the NPSP package. ## Frequently Asked Questions Get answers to questions about localization, including frequency, languages, and documentation. How often do you localize Salesforce.org products? We localize our product labels and text as part of every major seasonal release. What languages do you localize into? Salesforce.org localizes by package, not by product, so the languages vary. See [Available Languages](https://help.salesforce.com/s/articleView?id=sfdo.npsp_and_translation.htm&release=264.0.0&type=5 "See the list of languages available for NPSP."). Salesforce offers three levels of language support: fully supported languages, end-user languages, and platform-only languages. For more information, see [Supported Languages](https://help.salesforce.com/articleview?id=faq_getstart_what_languages_does.htm&type=5). Do you localize product documentation? We currently localize documentation for these products: Accounting Subledger, Accounting Subledger Legacy, Case Management, Education Cloud, Education Data Architecture (EDA), Grants Management, Insights Platform Data Integrity, Marketing Cloud Engagement for Industries, Nonprofit Cloud, Nonprofit Success Pack (NPSP), Outbound Funds Module, Program Management Module (PMM), and Student Success Hub (SSH). See [Available Languages](https://help.salesforce.com/s/articleView?id=sfdo.npsp_and_translation.htm&release=264.0.0&type=5 "See the list of languages available for NPSP.") for details. See [Localized Documentation](https://help.salesforce.com/s/articleView?id=sfdo.npsp_and_translation.htm&release=264.0.0&type=5 "Get links to documentation in other languages.") for a list of links to documentation. I noticed a mistake or something missing from a translation. Where do I report it? Keep in mind that we update translations only for major releases, so they can be out of sync after minor releases. To report a mistake, [create a case](https://help.salesforce.com/supportandservices) with the Topic set to Setup and Security, and the Category set to Globalization and Localization. Can I override translations? Absolutely. You can use the Translation Workbench to override translations. To learn more, see [Translation Workbench](https://help.salesforce.com/articleview?id=platform.workbench.htm&type=5). What's the difference between language and locale? In Salesforce, you'll see both Language and Locale settings. Locale determines the display formats for date and time, addresses, phone numbers, and commas and periods in numbers. Language determines the language that objects, fields, settings, and user interface text appear in. Do you accept translations from the community? Even though many of our products are open source, we don't currently accept GitHub pull requests for localization contributions. The localization process requires a level of maintenance that's not realistic or sustainable for community contributors, and we therefore rely on our own localization programs to deliver high-quality, timely translations. ## Available Languages See the list of languages available for NPSP. Salesforce.org provides translations into these languages. When you choose one of the supported languages during user (or org-wide) setup, NPSP objects, fields, settings, and user interface text appear in that language. ### Nonprofit Success Pack (NPSP) | Language | UI | Documentation | | --- | --- | --- | | Dutch | √ | √ | | English (UK) | √ | √ | | French | √ | √ | | German | √ | √ | | Hebrew | √ (partial) |   | | Japanese | √ |   | | Portuguese (Brazil) | √ | √ | | Spanish | √ |   | ### Tableau Dashboard Starters for Nonprofits ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/images/icon_note.png) Note These languages apply to the Fundraising Dashboard (included with NPSP) and Programs Dashboard (included with Case Management and PMM). | Language | UI | Documentation | | --- | --- | --- | | Dutch | √ |   | | English (UK) | √ |   | | French | √ |   | | German | √ |   | | Japanese | √ |   | | Spanish | √ |   | ### Unsupported Languages If we don't support your preferred language, you can localize your org to enable that language for your global users. One option is to use the Translation Workbench to translate your text customizations and override labels and translations from managed packages. You can translate everything from custom picklist values to custom fields. For more information, see [Add Translated Languages and Translators](https://help.salesforce.com/articleview?id=platform.adding_and_editing_translated_languages.htm&type=5) and [Translate Custom Labels](https://help.salesforce.com/articleview?id=platform.cl_translate_edit.htm&type=5). ## Localized Documentation Get links to documentation in other languages. Use these links to access the localized documentation for each available language. ### Nonprofit Success Pack - [Dutch](https://sfdo-docs.s3.us-west-2.amazonaws.com/localizedpdfs/npsp/nonprofit_success_pack_nl_nl.pdf) - [English (UK)](https://sfdo-docs.s3.us-west-2.amazonaws.com/localizedpdfs/npsp/nonprofit_success_pack_en_gb.pdf) - [French](https://sfdo-docs.s3.us-west-2.amazonaws.com/localizedpdfs/npsp/nonprofit_success_pack_fr_fr.pdf) - [German](https://sfdo-docs.s3.us-west-2.amazonaws.com/localizedpdfs/npsp/nonprofit_success_pack_de_de.pdf) - [Portuguese (Brazil)](https://sfdo-docs.s3.us-west-2.amazonaws.com/localizedpdfs/npsp/nonprofit_success_pack_pr_br.pdf) ## Enable Languages Enable localization in Salesforce for your NPSP product. We recommend that you complete these steps to enable a language for use in NPSP: 1. Before using any translated languages, enable Translation Workbench in Setup. For information, see [Enable and Disable the Translation Workbench](https://help.salesforce.com/articleview?id=customize_wbench.htm). 2. If you're enabling a platform-only language: 1. From Setup, search for and then select **Enable platform-only languages**. 2. Move the desired language to the Displayed Languages list. 3. Save your changes. ## Translation Limitations If you're localizing your org on your own, keep in mind that there are some issues and considerations due to the nature of the NPSP package. Here is a list of "trouble areas" in NPSP that cannot or should not be translated. In each area, we provide details on the appropriate way to handle the situation, whether it's translating the items on your own, or leaving things as-is. As we update the product, where possible, we are working to address gaps that prevent NPSP from being fully translated. Legacy Recurring Donations You can translate picklist values specific to Frequency, but do not translate the custom labels associated with Recurring Donation frequency. If you choose to translate the Frequency picklist values, keep in mind that when users in your org enter recurring donations, the Status should always be `None` or `Open` (i.e. the translated value associated with those picklist options). If users choose the translated value of `Closed`, the donations aren't created properly on the Recurring Donations related list. This is a known issue we are working to address. Translating the values of the custom labels for Recurring Donation Frequency will break the behavior that schedules the upcoming donations, so no donations are created. These custom labels should never be translated. They are internal-facing only so users are not negatively impacted. Relationships Relationships in NPSP have functionality that automatically creates a reciprocal based on the list settings in the NPSP Settings tab. Because reciprocal relationships are not packageable, we can only include them in installs or new trial orgs but we can't push translations to these values. Be very careful when translating the value of the picklists for Relationships and remember to translate the values in the NPSP Settings tab as well. Users can create new values in NPSP Settings by clicking **Relationships** | **Relationship Reciprocal Settings** | **New Reciprocal Relationship** and creating new values to match translated ones. If picklist values are translated but the Setting is not created, relationship reciprocals will not be created correctly. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/images/icon_note.png) Note If you don't see the **NPSP Settings** tab in your org, you can find it in the App Launcher. Data Import Mapping ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/images/icon_note.png) Note These restrictions apply only if you're using the Help Text method for mapping fields for the NPSP Data Importer; you can safely ignore this information if you're using Advanced Mapping. See [Map Custom Fields Using Help Text](https://help.salesforce.com/s/articleView?id=sfdo.npsp_map_using_help_text.htm&release=264.0.0&type=5 "NPSP legacy Help Text mapping allows you to reference additional fields on a small number of Salesforce objects through Help Text on the NPSP Data Import fields.") for more information. When users attempt to use the NPSP Data Importer and have translated the help text for the fields used within the NPSP Data Import object, the import process will fail. We recommend that you do not translate the help text for all fields on the NPSP Data Import object, as the help text on the NPSP Data Import object should be the Developer Name of the destination field. Household Naming Behind the scenes, NPSP uses some fields as it automatically names Household Account records and Household objects (if used). Translating these fields in the Translation Workbench will break the naming functionality: - PicklistValue.npo02\_\_Household\_\_c.npo02\_\_SYSTEM\_CUSTOM\_NAMING.Name - PicklistValue.Account.npo02\_\_SYSTEM\_CUSTOM\_NAMING.Name Other Picklist Values NPSP includes picklist values for Preferred Phone such as Home, Mobile, Work, etc. These values are referenced in Contact-specific workflow rules. If these values are translated, the workflow rules won't work. The workaround is to disable the NPSP workflow rules and create identical ones using the translated values. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/images/icon_note.png) Note The related workflow rules are off by default, so users may not experience any change in behavior when values are translated. The picklist values are: - PicklistValue.Contact.npe01\_\_PreferredPhone.Home - PicklistValue.Contact.npe01\_\_PreferredPhone.Mobile - PicklistValue.Contact.npe01\_\_PreferredPhone.Other - PicklistValue.Contact.npe01\_\_PreferredPhone.Work - PicklistValue.Contact.npe01\_\_Preferred\_Email.Alternate - PicklistValue.Contact.npe01\_\_Preferred\_Email.Personal - PicklistValue.Contact.npe01\_\_Preferred\_Email.Work There are additional picklist values available in Translation Workbench that are never surfaced to users. These shouldn't be translated so as to not break functionality: - PicklistValue.npsp\_\_Schedulable\_\_c.npsp\_\_Frequency.Daily - PicklistValue.npsp\_\_Schedulable\_\_c.npsp\_\_Frequency.Hourly - PicklistValue.npsp\_\_Schedulable\_\_c.npsp\_\_Frequency.Monthly - PicklistValue.npsp\_\_Schedulable\_\_c.npsp\_\_Frequency.Quarterly - PicklistValue.npsp\_\_Schedulable\_\_c.npsp\_\_Frequency.Weekly - PicklistValue.Contact.npe01\_\_SystemAccountProcessor.One-to-One - PicklistValue.Contact.npo02\_\_SystemHouseholdProcessor.All Individual Contacts - PicklistValue.Contact.npo02\_\_SystemHouseholdProcessor.All New or Edited Contacts - PicklistValue.Contact.npo02\_\_SystemHouseholdProcessor.No Contacts