Common Questions

How Can I Invite People to a Project?

When inviting new project members to your project, you can choose from current organization members or manually enter the email address of the person you want to invite. Before sending the invitation, you can specify what permissions the invitee should have in the project by selecting the needed roles and languages.

To invite people, open your project and go to the Members tab.

Read more about inviting people to a project.

How to Assign/Invite People to Particular Languages?

Depending on the project configuration (project with or without a workflow), you can grant access to all or selected target languages and all or selected workflow steps. You can set the preferred permissions during the invitation or once the invitees join the project.

For projects with a workflow, you can assign a workflow template with preconfigured target languages and assignees on each workflow step. Alternatively, you can assign people after you add a workflow to your project.

How Can I View Project Activities?

To view all project activities, open your project and go to the Activity tab. Use filters to find activities of specific types related to specific people or languages.

You can also go to the project’s Reports tab, Project Summary section, to see a progress timeline for translation and proofreading, and to check when the source strings were added, deleted, or updated.

How Can I Upload My Existing Translations to a Project?

If you have some existing translations, you can upload them via the Translations tab, language page, or Editor.

Read more about Uploading Existing Translations.

What Are Quality Assurance (QA) Checks?

QA checks are the automatic review of all translations against a set of rules such as translation consistency, spacing consistency, proper spelling, and more.

You can find the list of all QA check parameters and enable the necessary ones in the project’s Settings > Quality assurance.

If a QA check issue is detected in a translation, proofreaders can see it in the Editor.

Read more about QA Checks.

How to Assign Tasks to Project Members?

Tasks are one of the tools that help manage the localization process, especially for projects without a workflow, or when you need to split large files between translators or assign files to specific people. In these cases, you can create tasks within your project. Alternatively, if you have projects with a workflow, you can assign people to the translation and proofreading workflow steps and enable project notifications to avoid creating tasks.

To create tasks and assign them to project members, open your project and go to the Tasks tab.

Read more about Tasks.

How Can I Automate the Upload of Source Strings and Download of Translations?

Besides the possibility to upload source files and download translations manually via the web interface (UI), you can choose between the following options:

  • Integrate your Crowdin project with the tools you already use (e.g., VCS systems like GitHub, GitLab, Bitbucket, or Azure Repos; CMS systems, etc.). Explore the available integrations on the Crowdin Store.
  • Use API or console client (CLI).

You can also configure Webhooks to stay updated on key events in Crowdin Enterprise.

Combining the above options allows you to easily integrate localization into your company’s development process.

What Kind of Reports Can I Generate?

You can access the following types of reports:

  • Cost estimate – if you already know the rates of your translators, proofreaders, or vendors you can generate this report in advance to find out the approximate future localization cost.
  • Translation cost – with this report, you can calculate the actual localization cost based on the completed translation and proofreading.
  • Top members – this report is useful if you have a community involved in translation. Keep track of the most active members and reward them for their efforts.

The Reports section also includes charts with a project overview and information on project size, translation, proofreading activities, and more.

To generate reports, open your project and go to the Reports tab.

Read more about Reports.

How Can I Upload Translation Memories (TMs) And Glossaries?

If you have your existing translation memory and glossary files, you can upload them to Crowdin Enterprise in TMX, CSV, or XLSX file formats for translation memories and in TBX, CSV, or XLSX formats for glossaries.

Open your organization’s Workspace and select Translation Memories or Glossaries on the left sidebar to upload localization resources directly to your organization. Once uploaded, you can assign these localization resources to the needed projects.

Read more about Translation Memory and Glossary.

How Do I Handle Duplicates in Crowdin Enterprise?

Your project may contain duplicate strings, especially if you translate multiple branches. Any unique source string that was first uploaded or added to the project is considered a master string. Other strings that are identical to the master string by source text or source text and key (depending on whether you are using regular or strict duplicate detection) but were uploaded or created later are considered duplicate strings. If you choose to automatically translate duplicate strings, they will share the translations of the master strings.

Open your project and go to Settings > Import to choose how Crowdin Enterprise should handle duplicates using the following options:

  • Show – translators will translate each instance separately
    This option is enabled by default. Use it when duplicates are used in a different context and thus should be translated differently.

  • Show, but auto-translate them
    Duplicates will be shown in the Editor but will be auto-translated once the source string is translated. This option is used in rare cases when some duplicates require unique translations, and the others should be auto-translated.
    Note: If the master string has no translations, duplicates won’t be auto-translated.
  • Show within a version branch – duplicates will be hidden only between version branches
    All the duplicates within your master branch will be visible and translated separately. The duplicates in the version branches will be hidden and auto-translated.
    Note: When working with several branches, first integrate your master branch with Crowdin Enterprise and then the other branches.
  • Hide – all duplicates will share the same translation If the duplicates are used in the same context, you can save time by hiding them in the Editor and auto-translating them. In this case, only a master string will be visible to translators working in the Editor.

Both Show within a version branch and Hide options are available in two versions: regular duplicate detection and strict duplicate detection. If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of the option. In other cases, feel free to use a regular one.

Read more about Duplicate Strings.

How to Hide a String from Displaying in the Editor?

If your project contains some strings that should not be translated or should be translated later, you can hide these strings from translators. You can hide selected strings or all strings within a file.

To hide strings, open your project and go to Sources > Strings.

Read more about Changing Strings Visibility.

Alternatively, you can also hide strings in the Editor. In the upper-middle section, click and select Hide String. When the hidden strings are ready for translation or proofreading, you can use the filter to find them in the Editor and make these strings visible again.

Was this article helpful?