Vendor-restricted File within a public project

Hello, within our publicly accessible project, we would like to specify a single file to be translated exclusively by the vendor, not by the community. Could someone please help me with the solution, as Crowdin is not very straightforward for this? I had thought the restriction was already in place due to the original assignment to a specific vendor, but sadly, it’s not.

Thank you for your guidance!

1 Like

Hi @Niki_windy-com In case you’re using crowdin.com. It is better to implement such workflow within two separate projects. To a newly created private project, you can add your file and create tasks for your vendors

If you’re using Crowdin Enterprise, it is possible to create the following workflow and by creating tasks you’ll be able to manage which content should be sent to the vendor for translation:

Here you can find more regarding the Translation and Proofreading by Vendor workflow step:

1 Like

Thank you but as there was already work done on translations in the existing project I would prefer to deal with it differently this time. Any idea? Next time I will work with separate private project.

Hi @Niki_windy-com

Technically, it’s not possible, sorry to say. Only the 2-projects approach will work for you.

Since there’s already work done on translations in the existing project, you can migrate the content to a new project without starting from scratch. Here’s a brief outline of the steps you can follow:

  1. Download the source files from your current project.
  2. Download the existing translations.
  3. Create a list of participants’ usernames/permissions locally.
  4. Re-invite them into the new project.
  5. Re-create a project under your new account.
  6. Re-upload the sources and translations into the new project.

This way, you can preserve the work already done and continue in a separate project.

Hi Niki,

If you’re using crowdin.com, you may create the task to translate by the vendor and include only one file:
Project Tasks | Crowdin Docs