diff --git a/src/content/docs/crowdin/project-management/project-settings/privacy-collaboration.mdx b/src/content/docs/crowdin/project-management/project-settings/privacy-collaboration.mdx
index 548d350a..d47801fd 100644
--- a/src/content/docs/crowdin/project-management/project-settings/privacy-collaboration.mdx
+++ b/src/content/docs/crowdin/project-management/project-settings/privacy-collaboration.mdx
@@ -8,6 +8,7 @@ sidebar:
---
import { Aside } from '@astrojs/starlight/components';
+import ReadMore from '~/components/ReadMore.astro';
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.
@@ -27,16 +28,14 @@ This section controls your project's visibility, member access, and general coll
* **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.
-
+* **Task-based access control** – Restricts translators and proofreaders to work only with strings included in their assigned translation or proofreading tasks.
+
+ Read more about [Task-based access control](/tasks/#task-based-access-control).
+
* **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.
diff --git a/src/content/docs/crowdin/tasks/tasks.mdx b/src/content/docs/crowdin/tasks/tasks.mdx
index 7ac42844..74fa01c0 100644
--- a/src/content/docs/crowdin/tasks/tasks.mdx
+++ b/src/content/docs/crowdin/tasks/tasks.mdx
@@ -359,13 +359,15 @@ Sequential tasks are available for the following task types:
* Pending proofreading tasks can be deleted if necessary. In this case, linked translation tasks are preserved.
* Deleting a translation task with an associated sequential proofreading task results in the deletion of both tasks simultaneously.
-## See Also
+## Task-based Access Control
+
+When [Task-based access control](/project-settings/privacy-collaboration/#privacy) is enabled, translators and proofreaders can work with strings only through tasks assigned to them. On language pages, users see a warning that access to strings is available only through assigned tasks. If they try to open content outside those tasks in the Editor, they will see a warning popup.
+
+In the **Tasks** tab, users can still view task cards, but they can open in the Editor only the tasks assigned to them. Regular language permissions are not used to grant editing or approval access while this option is enabled.
-
+This restriction applies to translators and proofreaders. Project members with language coordinator permissions or higher keep access according to their roles. For example, a translator with permission to work on French who is assigned to a task in German can work in the Editor only within the assigned German task.
+
+## See Also
- 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.
+ This restriction applies to translators and proofreaders. Project members with language coordinator permissions or higher keep access according to their roles.
+
+ Read more about [Task-based access control](/enterprise/tasks/#task-based-access-control).
+
## Glossary Access Settings
@@ -34,7 +34,7 @@ Configure the preferred glossary access level with the following options:
* **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.
-## Task Cross-Review :badge[New]{variant=success} {#task-cross-review}
+## Task Cross-Review
Require approval from selected managers or the owner before contributors can start working on a task. This feature adds an additional review step, helping maintain accountability and oversight in task workflows.
diff --git a/src/content/docs/enterprise/tasks/tasks.mdx b/src/content/docs/enterprise/tasks/tasks.mdx
index 838d30ff..6ea7f16e 100644
--- a/src/content/docs/enterprise/tasks/tasks.mdx
+++ b/src/content/docs/enterprise/tasks/tasks.mdx
@@ -346,7 +346,15 @@ Sequential tasks are available for the following task types:
* Pending proofreading tasks can be deleted if necessary. In this case, linked translation tasks are preserved.
* Deleting a translation task with an associated sequential proofreading task results in the deletion of both tasks simultaneously.
-## Task Cross-Review :badge[New]{variant=success} {#task-cross-review}
+## Task-based Access Control
+
+When [Task-based access control](/enterprise/project-settings/privacy/#translations) is enabled, translators and proofreaders can work with strings only through tasks assigned to them. On language pages, users see a warning that access to strings is available only through assigned tasks. If they try to open content outside those tasks in the Editor, they will see a warning popup.
+
+In the **Tasks** section, users can still view task cards, but they can open in the Editor only the tasks assigned to them. Regular language permissions are not used to grant translation or approval access while this option is enabled.
+
+This restriction applies to translators and proofreaders. Project members with language coordinator permissions or higher keep access according to their roles. For example, a translator with permission to work on French who is assigned to a task in German can work in the Editor only within the assigned German task.
+
+## Task Cross-Review
The **Task Cross-Review** feature helps ensure proper oversight in task workflows by requiring approval before contributors can start working. It’s especially beneficial for teams with internal approval processes, such as budget approvals, where tasks must be reviewed and approved by designated managers or the owner. By adding an extra layer of accountability, this feature ensures tasks don’t move forward without proper review.
@@ -370,12 +378,6 @@ Only selected managers or the owner can approve the task. The manager who create
## See Also
-
-