Privacy & Collaboration Settings

In the Privacy & Collaboration section of the Project Settings you can manage the visibility of your project and its contents. You can also configure the notifications sent to project participants.

Project visibility

Set the preferred visibility for your project with the following options:

• Public project – public projects can be found via search engines and Crowdin search. Crowdin users can join public projects without approval if the Moderated project joining option is disabled.
• Private project – private projects can’t be found via search engines and Crowdin search. Only the invited users can join the project.

Privacy

Configure your project privacy settings with the following options:

• Two-factor authentication – specify which project members are required to enable two-factor authentication in their Account Settings > Account tab to access the private project. This role-based option provides the following configurations:
  • Turned off – two-factor authentication is not required (default).
  • All project members – requires all project members to enable two-factor authentication, disabling other member category options.
  • Managers – requires only members with the Manager role to enable two-factor authentication.
  • Developers – requires only members with the Developer role to enable two-factor authentication. You can select the Managers and Developers options individually or together. After selecting your preferred categories, click Update to save changes.
• Moderated project joining – require users to send requests to join the translation team of the preferred language. After the review, a project manager or proofreader can approve or decline the request. After joining the project, multilingual translators can submit new requests to join translation teams in other target languages.
• 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.

  Note

  Users with any role (like translators, proofreaders) in your project will still have access to the content! To restrict access to content assigned to users via tasks:

  • Invite users to the project without a role.
  • Create a task and assign it to a user.
• 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 proofreaders to access hidden strings – allow proofreaders to work with hidden strings. The project owner and managers can always work with hidden strings, not depending on the option status.

Glossary Access Settings

Control the level of access that project members have over glossary terms. The project owner and managers always have full control over glossary terms, regardless of these settings.

Configure the preferred glossary access level with the following options:

• Read only – allow members to view existing glossary terms without the possibility to modify them. This option provides access for reference only.
• Manage drafts – allow members to view, add, edit, and delete draft glossary terms, and view approved terms. This option allows members to contribute to drafts without altering approved terms.
• Full access – allow members to view, add, edit, and delete glossary terms, as well as edit concept details. This option provides members with full control over glossary terms and their details.

Notifications

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.