docs: Glossary Access Settings, Two-factor authentication (#172)

src/content/docs/crowdin/localization-resources/glossary.mdx

@@ -78,7 +78,7 @@ Term details:
 * Language – specifies the language of the term.
 * Part of speech – e.g., noun, verb, adjective, etc.
 * Type – e.g., full form, acronym, abbreviation, etc.
-* Status – preferred, admitted, not recommended, obsolete.
+* Status – preferred, admitted, not recommended, obsolete, draft.
 * Gender – term gender.
 * Description – term description.
 * Note – short notes about a term that might be helpful to translators.
@@ -111,9 +111,13 @@ To allow translators and proofreaders to manage terms in the Editor, follow thes
 
 <Steps>
   1. Open your project and go to **Settings > Privacy & collaboration**.
-  2. In the **Privacy** section, select *Allow project members to manage glossary terms*.
+  2. In the [**Glossary Access Settings**](/project-settings/privacy-collaboration/#glossary-access-settings) section, select the preferred access level for project members.
 </Steps>
 
+You can choose to allow them to manage only draft terms. When a project member adds a draft term, project managers can filter terms by draft status, review them, and make necessary modifications or add glossary concept details.
+
+Alternatively, you can grant full access, allowing them to manage all glossary terms and concept details with the same level of control as the project owner and managers.
+
 ### Viewing and Filtering Glossary Concepts and Terms
 
 Once you open a glossary, you can view and filter its glossary concepts and terms using either the Concepts or Terms pages.
@@ -144,7 +148,7 @@ By default, all glossary concepts and terms are displayed in the Concepts and Te
 * Modified: All, Custom Range.
 * Part of speech: All, Adjective, Adposition, Adverb, Auxiliary, Coordinating conjunction, Determiner, Interjection, Noun, Numeral, Pronoun, Proper noun, Particle, Subordinating conjunction, Verb, Symbol, Other.
 * Type: All, Full form, Acronym, Abbreviation, Short form, Phrase, Variant.
-* Status: All, Preferred, Admitted, Not recommended, Obsolete.
+* Status: All, Preferred, Admitted, Not recommended, Obsolete, Draft.
 * Gender: All, Masculine, Feminine, Common, Neuter, Other.
 * Author: All, particular user.
 

src/content/docs/crowdin/project-management/project-settings/privacy-collaboration.mdx

@@ -22,7 +22,12 @@ Set the preferred visibility for your project with the following options:
 
 Configure your project privacy settings with the following options:
 
-* **Require two-factor authentication for all the project members** – request project participants to enable two-factor authentication in their **Account Settings > Account** tab to access the private project.
+* **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.
   <Aside>
@@ -33,7 +38,16 @@ Configure your project privacy settings with the following options:
   </Aside>
 * **Allow offline translation** &ndash; 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** &ndash; allow proofreaders to work with hidden strings. The project owner and managers can always work with hidden strings, not depending on the option status.
-* **Allow project members to manage glossary terms** &ndash; 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.
+
+## Glossary Access Settings :badge[New]{variant=success} {#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** &ndash; allow members to view existing glossary terms without the possibility to modify them. This option provides access for reference only.
+* **Manage drafts** &ndash; 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** &ndash; 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
 

src/content/docs/enterprise/localization-resources/glossary.mdx

@@ -79,7 +79,7 @@ Term details:
 * Language – specifies the language of the term.
 * Part of speech – e.g., noun, verb, adjective, etc.
 * Type – e.g., full form, acronym, abbreviation, etc.
-* Status – preferred, admitted, not recommended, obsolete.
+* Status – preferred, admitted, not recommended, obsolete, draft.
 * Gender – term gender.
 * Description – term description.
 * Note – short notes about a term that might be helpful to translators.
@@ -112,9 +112,13 @@ To allow translators and proofreaders to manage terms in the Editor, follow thes
 
 <Steps>
   1. Open your project and go to **Settings > Privacy**.
-  2. In the **Translations** section, select *Allow project members to manage glossary terms*.
+  2. In the [**Glossary Access Settings**](/enterprise/project-settings/privacy/#glossary-access-settings) section, select the preferred access level for project members.
 </Steps>
 
+You can choose to allow them to manage only draft terms. When a project member adds a draft term, project managers can filter terms by draft status, review them, and make necessary modifications or add glossary concept details.
+
+Alternatively, you can grant full access, allowing them to manage all glossary terms and concept details with the same level of control as the project owner and managers.
+
 Enhance terminology consistency across your project by setting up AI Alignment. This feature automatically generates draft glossary terms based on translations suggested by human translators, helping maintain preferred terminology.
 
 <LinkCard
@@ -152,7 +156,7 @@ By default, all glossary concepts and terms are displayed in the Concepts and Te
 * Modified: All, Custom Range.
 * Part of speech: All, Adjective, Adposition, Adverb, Auxiliary, Coordinating conjunction, Determiner, Interjection, Noun, Numeral, Pronoun, Proper noun, Particle, Subordinating conjunction, Verb, Symbol, Other.
 * Type: All, Full form, Acronym, Abbreviation, Short form, Phrase, Variant.
-* Status: All, Preferred, Admitted, Not recommended, Obsolete.
+* Status: All, Preferred, Admitted, Not recommended, Obsolete, Draft.
 * Gender: All, Masculine, Feminine, Common, Neuter, Other.
 * Author: All, particular user.
 

src/content/docs/enterprise/project-management/project-settings/privacy.mdx

@@ -13,9 +13,8 @@ In the **Privacy** section of the Project Settings, you can manage the visibilit
 
 ## Translations
 
-* **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](/enterprise/machine-translation/) 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.
+* **Allow proofreaders to access hidden strings** – allow proofreaders to work with hidden strings. Members with manager permissions or higher can always work with hidden strings, 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.
   <Aside>
     Users with any role (like translators, proofreaders) in your project will still have access to the content!
@@ -24,6 +23,16 @@ In the **Privacy** section of the Project Settings, you can manage the visibilit
     - Create a task and assign it to a user.
   </Aside>
 
+## Glossary Access Settings :badge[New]{variant=success} {#glossary-access-settings}
+
+Control the level of access that project members have over glossary terms. Members with manager permissions or higher always have full control over glossary terms, regardless of these settings.
+
+Configure the preferred glossary access level with the following options:
+
+* **Read only** &ndash; allow members to view existing glossary terms without the possibility to modify them. This option provides access for reference only.
+* **Manage drafts** &ndash; 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** &ndash; 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.