Projektindstillinger kan opsættes jf. egne behov via fanen Indstillinger.

For convenient navigation, all project settings are grouped as follows:

  • Generelt
  • Fortrolighed
  • Languages
  • Quality assurance
  • Translation memories
  • Glossaries
  • Import
  • Export
  • Parser configuration

Project settings



In the Details section, you can upload the project logo, change the project name, view the Project ID within your organization, and add a short description.

Project details

Transfer Ownership

Originally, you own any project you create in Crowdin Enterprise. You can transfer your project ownership to any other user in the Organization you belong to.

Click Transfer and select the needed user to transfer ownership. New project owner will have access to all project resources and will be able to remove the project.

Transfer ownership

Slet projekt

This option is accessible to project managers, project owner, parent group managers, and organization admins. You can delete the Crowdin Enterprise project with all the translations and related localization resources.

Note! This action can't be undone.

Delete project



  • Show machine translation suggestions – enable MT suggestions from machine translation engines such as Microsoft Translator, Google Translate, and others to be displayed in the Editor. The organization admin should configure machine translation engines before using them.
  • Allow Offline Translation – allow translators to download source files to their machines for offline translation and upload translations back into the project. The project owner and managers can always download sources and upload translations, not depending on the option status.
  • Allow project members to manage glossary terms – allow translators and proofreaders to add new glossary terms to the project. The project owner and managers can always add and edit glossary terms, not depending on the option status.
  • Task-based access control – allow project members to work with tasks they are assigned to, even if they do not have full access to the language in the project.

Project settings translations


Project notifications are disabled by default. Enable the necessary notifications for an agile translation process. Such approach helps to avoid creating additional tasks for every contributor.

  • Notify translators about new strings – translators will receive an email notification about newly added content for translation each time after the update. The Receive emails option should be activated in the translator’s profile.
  • Notify project managers and developers about new strings – project managers will receive an email notification about newly added content for translation each time after the update.
  • Notify project managers and developers about language translation/proofreading completion – project managers will receive the notification when some target language (all source files) is fully translated or fully proofread.



In the Languages section, you can manage your project source and target languages and configure language mapping to use custom language codes.

Source Language

If you want to change the source language for your project, select a new language from the drop-down list and click Save.

Here are a few points you should be aware of when changing the project’s source language:

  • Bemærk, at der kan optræde flertalsformsuoverensstemmelser for importerede strenge afhængigt af det nye kildesprog. Visse flertalsformer kan f.eks. ikke vises i Redigeringsværktøjet, eller visse flertalsoversættelser anvendes måske i andre ifm. oversættelseseksport. Det anbefales at opdatere kildefilerne, hvis det nye kildesprog har andre flertalsformer end det oprindelige.
  • Havde Redigeringsværktøjet en åben browser-fane under kildesprogopdateringen, kan det være nødvendigt at opfriske den for at effektuere ændringerne og fortsætte med oversættelsen på det nye kildesprog.

Source Language


The Target Languages section allows you to add or remove target languages in your project, copy the target languages list from one project to another, and add custom languages.



Add custom language codes and use them for translation files export. This will keep the structure of exported files consistent.

For example, in the screenshot below two custom codes are set for Greek language. If any of custom placeholders (2 letters, 3 letters codes) is used during file export the file name will include these specific language codes (GK, GEK).

Language mapping

Quality Assurance

In the Quality Assurance section, you can manage the types of QA issues to be highlighted in the Editor during the translation process.

Read more about Quality Assurance Checks.



The project TM is automatically created for each project. Therefore, every approved or last added translation is automatically saved in the project TM.

  • Auto-substitution – the feature substitutes the non-translatable elements (such as tags, HTML entities, placeholders, numbers, and more) in TM translation suggestions with the ones used in the source text. The feature improves the TM suggestions applied during pre-translation and those shown as translation suggestions in the Editor. Improved suggestions are included in the Translation Costs report, and improvable ones are included in the Costs Estimation report.
  • TM Suggestions for Dialects – the feature allows you to enable the displaying and use of TM suggestions from the primary language for dialects if no dialect-specific suggestions are available.

Translation Memory Settings

In the Assigned translation memories section, you can assign and manage the translation memories for your project.

Read more about Translation Memory.

Project translation memory


In the Glossaries section, you can assign and manage the glossaries for your project.

Read more about Glossary.

Glossaries Settings


Source Strings

  • Unify placeholders – if your project contains iOS strings, iOS XLIFF, and Android XML files, you can enable the Unify placeholders option, and the system will transform placeholders into a unified look. For example, Crowdin will make the Android string Hello, %s!, and the iOS string Hello, %@! look in the Editor this way: Hello, [%s]!. This option is beneficial when you work with TM since TM suggestions from iOS strings, iOS XLIFF, and Android XML will be completely interchangeable. Crowdin will transform the translation placeholders back to the original format on export. This option only applies to iOS strings, iOS XLIFF, and Android XML formats.
  • Save context information in the files – the context and max.length added in Crowdin Enterprise will be visible in the downloaded files. This option only applies to CSV, Android XML, iOS strings, and RESX formats. <div class="alert alert-info"> Note: This option only partially applies to iOS strings and RESX formats (i.e., only the context added in Crowdin Enterprise will be visible in the downloaded files).
  • Duplicate Strings – if your project contains duplicated strings, you can choose how the system should treat them using the following options:

    • Vis – oversættere håndterer hver forekomst (streng) individuelt. Duplicate strings won’t be hidden.
    • Show, but auto-translate them – Duplicate strings will be automatically translated but will stay visible to translators. Når strengen er oversat, deles dens oversættelse automatisk til dubletterne. Oversættere kan, om nødvendigt, gennemgå og omsætte disse strenge.
    • Show within a version branch (regular detection) – duplicates will be hidden only between version branches.
    • Vis indenfor en versionsgren (strikd detektering) – dubletter skjules kun mellem versionsgrene.
    • Skjul (alm. detektering) – alle dubletter deler den samme oversættelse.
    • Skjul (striks detektering) – alle dubletter deler den samme oversættelse.

Almimdelig dubletdetektion – ved sammenligning af strenge, tager Enterprise kun hensyn til kildetekster.
Striks dubletdetektering – ved sammenligning af strenge, tager Enterprise hensyn til både strengeidentifikatorer (nøgler) og kildetekster.

If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of the Duplicate Strings options. In other cases, feel free to use a regular one.

Read Duplicated Strings article for more details on duplicates management.

Source Strings

Word count

You can set the preferred way Crowdin Enterprise should count words in your project. Specifically, it applies to whether HTML tags should be counted as regular words or not. By default, Crowdin Enterprise considers HTML tags as regular words for most of the supported formats, excluding the following ones: HTML, Front Matter HTML, HAML, MD, Front Matter MD, XML, WEBXML, IDML, XLIFF, XLIFF 2.0, ADOC, DOCX, MIF, DITA.

  • Auto (standard) – afhængigt af kildefilformatet, tælles HTML-tags som alm. ord eller overspringes.
  • Tæl tags – alle HTML-tags tæller som alm. ord.
  • Overspring tags – ingen HTML-tags tælles.

When you change the word count option, only newly uploaded words will be counted according to the new settings. So it’s recommended to set the preferred word count settings before uploading source files to the project.

Word count

Custom placeholders

With Custom placeholders you can modify a list of placeholders that will be highlighted in the source strings in the Editor.

Tilpassede variabler

Read Custom Placeholders article for more details on how to add and work with custom placeholders.


By default, when exporting translations, Crowdin Enterprise fills untranslated strings with source text to avoid exporting empty files.

You can configure export options using the following settings:

  • Export strings with at least 1 translation – Choose if you want to export all translated strings without approval.
  • Export translations with a specific number of approvals – Choose if you want to export only strings with approved translations. Make sure the number of required approvals set isn’t higher than the actual number of proofreading steps in your project workflow.
  • Automatically fill in regional dialects – useful when the project is translated into the language dialects (e.g., Spanish, Argentina). On export, translations from Spanish will be automatically copied to untranslated strings in Spanish, Argentina.
  • Skip untranslated strings – only translated strings will be included in the exported translation files.

    Denne indstilling fungerer på tre forskellige måder, afhængigt af filformatet. This option is not applied to text-formatted documents since missing texts can make downloaded files unreadable. Andre eksporteres med tomme værdier. For den tredje filkategori fjernes uoversatte strenge helt fra de eksporterede oversættelsesfiler.

    Valgmulighed ikke anvendt Uoversatte strenge eksporteret med tomme værdier Uoversatte strenge fjernet
    DOCX, IDML, DITA, ADOC, MD, MediaWiki, TXT, HAML, HTML, assets, FM MD, FM HTML, Contentful JSON, SVG JSON (med indlejret struktur), PHP, XLSX, CSV, FJS, RC, XAML, XML, Web XML, TypeScript, JS, TOML, QT TS, i18next JSON, gettext PO, FLSNP, Coffee Android XML, macOS/iOS Strings, Stringsdict, Chrome JSON, JSON (without nested structure), YAML, XLIFF, XLIFF 2.0, ARB, DTD, RRC, GO JSON, Flex, Joomla INI, Maxthon, Java Properties, Play Properties, Java Properties XML, RES JSON, RESW, RESX, SBV, STR, STF, VTT, WXL, VDF, FBT JSON
  • Skip untranslated files – only translated files will be included in the exported translation archive.
    Bemærk: er denne indstilling aktiveret, tilsidesættes indstillingen Overspring uoversatte strenge.

Click Advanced Options to add separate export settings for specific project languages.

Export options

Parser Configuration

By default, Crowdin Enterprise uses a predefined set of import and export parameters for each supported file format.

With Parser configuration, you can change some of these settings according to your needs.

Read more about Parser configuration.

Parser Configuration

Var denne artikel nyttig?