Skip to content

Privacy & Collaboration Settings

In the Privacy & collaboration section of the project Settings tab, you can configure your project’s security and access rules, set glossary permissions, and manage team notifications.

This section controls your project’s visibility, member access, and general collaboration settings.

  • Two-factor authentication – Define which roles are required to have two-factor authentication (2FA) enabled to access the project. Users can enable 2FA in their Account Settings > Account tab. 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 2FA.
    • Managers – Requires only members with the Manager role to enable 2FA.
    • Developers – Requires only members with the Developer role to enable 2FA. You can select the Managers and Developers options individually or together. After selecting your preferred categories, click Update to save changes.
  • Project Visibility – Set the preferred visibility for your project:
    • Public project – Visible to everyone. The project will appear in the global Crowdin search results and be indexed by search engines.
    • Private project – Visible only to the invited project members.
  • Moderated project joining – When enabled, users can become translators for a specific language only after their join request is approved by a manager or language coordinator.
    • For Public projects, this setting is optional. You can enable it to review and approve new members before they can start contributing.
    • For Private projects, this setting is enabled by default and cannot be changed. All project members must be invited, and this setting ensures their access to specific languages is properly managed upon joining.
  • Task-based access control – Project members can be assigned specific translation or proofreading tasks for languages without having permanent access to them. This allows you to invite contributors to work only on the content within a task.
  • Allow offline translation – Allows translators to download source files to their machines and upload translations back into the project. Project owner and managers can always download sources and upload translations.
  • Allow proofreaders to access hidden strings – Allows proofreaders to work with hidden strings. Project owner and managers can always access hidden strings.

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

  • Read only – Members can view existing glossary terms but cannot make any changes. This option provides access for reference only.
  • Manage drafts – Members can view, add, edit, and delete draft glossary terms, and can also view approved terms. This allows members to contribute to drafts without altering the official, approved terminology.
  • Full access – Members can view, add, edit, and delete glossary terms and edit concept details. This provides members with full control over the project glossary.

Enable email notifications to keep project members informed about new content and progress, which helps you avoid creating a separate task for each update.

  • Notify translators about new strings – Translators will receive an email notification whenever new content for translation is added to the project.
  • Notify project managers and developers about new strings – Project managers will receive an email notification whenever new content for translation is added to the project.
  • Notify project managers and developers about language translation/proofreading completion – Project managers will receive a notification when a target language is fully translated or proofread.
Was this page helpful?