Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,8 @@ sidebar:
label: Privacy
---

import { Aside } from '@astrojs/starlight/components';
import { Aside, Steps } from '@astrojs/starlight/components';
import ReadMore from '~/components/ReadMore.astro';

In the **Privacy** 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.

Expand All @@ -23,7 +24,7 @@ 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}
## 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.

Expand All @@ -33,6 +34,26 @@ Configure the preferred glossary access level with the following options:
* **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.

## Task Cross-Review :badge[New]{variant=success} {#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.

<ReadMore>
Read more about [Task Cross-Review](/enterprise/tasks/#task-cross-review).
</ReadMore>

### Configuring Task Cross-Review

To enable and configure Task Cross-Review, follow these steps:

<Steps>
1. Enable the **Task Cross-Review** option in the **Tasks** section.
2. Select at least one manager responsible for approving tasks. You can search for managers by name, username, or email.
3. Click **Save** to apply the changes.
</Steps>

New tasks created after enabling **Task Cross-Review** will require approval, while existing tasks remain unaffected.

## 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.
Expand Down
23 changes: 23 additions & 0 deletions src/content/docs/enterprise/tasks/tasks.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ import edit from '!/enterprise/tasks/tasks_edit.png';
import filter from '!/enterprise/tasks/tasks_filter.png';
import move from '!/enterprise/tasks/tasks_move.png';
import close from '!/enterprise/tasks/tasks_close.png';
import pendingCrossReviewTasks from '!/enterprise/tasks/tasks_pending_cross_review_tasks.png'

Create and assign tasks for translating or proofreading content to specific project members or vendors. You can set due dates, split words among assignees, receive notifications about task changes and updates, and discuss tasks with other project members in the comments.

Expand Down Expand Up @@ -206,6 +207,28 @@ 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}

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.

<Image src={pendingCrossReviewTasks} alt="Pending Cross-Review Task" />

### How Task Cross-Review Works

When **Task Cross-Review** is enabled:

* During task creation, a notification informs the user that the task will require approval from eligible project members (selected managers or the owner) before assigned members can start working.

* On the Board, tasks awaiting approval display an alert indicating they are pending review from selected managers or the owner, making them easy to identify.

* In the task details view, an alert states, *"The task is currently pending review from selected managers or the owner,"* and the task is labeled with the status **For Approval**.

Only selected managers or the owner can approve the task. The manager who created the task cannot approve it, but the owner can always approve their own tasks. Once approved, the task status changes to **<span style={{ whiteSpace: 'nowrap' }}>To Do</span>**, indicating that contributors can begin work.

<ReadMore>
Read more about [configuring Task Cross-Review](/enterprise/project-settings/privacy/#configuring-task-cross-review).
</ReadMore>

## See Also

<LinkCard
Expand Down
Loading