> For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt.

# Triage

Triage is a Space inbox for inbound tasks from integrations and read-only members. Review each task, set its priority, then accept or decline it before it enters the Space workflow.

Triage is off by default. The sidebar entry appears only after you enable it for that Space. Inbound submissions enter the **Triage status** only while the inbox is on.

Enable it when a Space receives work from connected integrations, Organization members who are not in the Space, or Private Space Viewers, and that work should be reviewed before it appears on boards. If Space members create all of the work from the ordinary task page, you usually do not need the Triage inbox.

## How it differs from nearby concepts

The product uses **Triage** for both the inbox and the status. This page distinguishes them as the **Triage inbox** and the **Triage status**.

| Concept       | What it is                                          | What it is not                                                   |
| ------------- | --------------------------------------------------- | ---------------------------------------------------------------- |
| Triage inbox  | A Space module, sidebar entry, and review queue     | Not a task type                                                  |
| Triage status | The status category for work waiting to be reviewed | Not another name for the inbox entry                             |
| Inbox         | A personal notification center                      | Not the Space-level review queue                                 |
| Backlog       | The regular workflow's parking area                 | Where current Triage-status tasks move if you turn the inbox off |

Triage rules in Space settings are also not [Automations](/docs/space/automations.md) or [Automation workflows](/docs/space/automation-workflows.md).

## Enable the Triage inbox

Path: Space settings → Triage.

- Organization Owners, Organization Admins, and Space Administrators can change the setting. Other people can view it but cannot edit it.
- It is off by default. You can select the **Triage** module when creating a Space, and you can still turn it on or off later in settings. Space settings are the only gate; there is no account-level beta switch.
- After you enable it, **Triage** appears under that Space in the sidebar.
- The settings page explains that tasks added by read-only members are sent to the Triage inbox first.
- Optional: **Require explicit prioritization**. A task in the Triage status must have a priority before it enters the regular workflow or is assigned to a [Sprint](/docs/space/sprints.md).

## Which tasks enter the Triage inbox

This applies only when the Space has the Triage inbox enabled and the task type's Workflow includes a Triage status. If the inbox is off, or the Workflow has no Triage status, task creation still succeeds and uses that type's own default status. After you import task types from Jira or other external tools, those types also include a Triage status once the inbox is on. New tasks that match the Triage rules then appear in the inbox, instead of looking as if they were never created.

| Source                                                                                           | Enters Triage                      | Notes                                                                                 |
| ------------------------------------------------------------------------------------------------ | ---------------------------------- | ------------------------------------------------------------------------------------- |
| A Space member creates a task from the ordinary task page                                        | No                                 | Uses the task type's default status                                                   |
| **Create triage task** on the Triage page, or `C`                                                | Yes                                | Members can file work into the queue on purpose                                       |
| An Organization member who is not in the Space submits to it                                     | Yes                                | Choosing another status does not bypass this                                          |
| New work created by a connected Jira sync, or a newly opened GitHub issue in a linked repository | Yes                                | One-time historical imports follow status mapping and do not necessarily enter Triage |
| A Viewer in a Private Space creates a task                                                       | Yes, and only in the Triage status | If the inbox is off, Viewers cannot create tasks                                      |
| An Organization Owner or Admin explicitly chooses another status                                 | No                                 | The task can enter the regular workflow                                               |

Public Space Viewer limits follow the product. Organization **Guest** and Space **Viewer** are different roles. See [People](/docs/space/members.md).

## Use the Triage inbox

The page shows the queue on the left and the selected task on the right. On a narrow layout, only one side is visible at a time.

In the list you can:

- See how many tasks are waiting in the Triage status
- Filter with the same filters as the task list
- Sort by **Added to triage**, ascending or descending
- In display options, show ID, due date, and **Show snoozed**
- Favorite the Triage entry
- See current Triage responsibility at the top and open **Configure triage responsibility**

Use the action bar at the bottom of the detail pane:

| Action         | Shortcut             | Result                                                                                                                                                                                                   |
| -------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Accept         | `1`                  | Leaves the Triage status and moves to the task type's default Workflow status, usually Unstarted. You can add a comment, change assignee, priority, labels, Project, and dates, and subscribe to updates |
| Mark duplicate | `2`, or `M` then `M` | Choose an existing task as the target. The current task enters a Duplicate terminal status. You cannot paste a link from another Organization                                                            |
| Decline        | `3`                  | Moves to a Canceled status. You can write a decline reason                                                                                                                                               |
| Snooze         | `H`                  | Hides the task until the chosen time, then returns it to the queue. Use **Show snoozed** to see it, or cancel the snooze                                                                                 |

If you still need more information, comment in the Triage inbox or snooze the task. Do not accept it first.

Bulk **Accept**, **Decline**, and **Snooze** appear only when every selected task is in the Triage status. Decline can use one shared reason.

If the Space requires explicit prioritization, a task without a priority cannot be accepted, moved to a regular status, or added to a Sprint.

Other shortcuts do nothing while you are typing in an input: `J` / `K` move up and down, and `C` creates a task in the Triage status.

## Triage responsibility

Path: Space settings → Triage → Triage responsibility. You can also open **Configure triage responsibility** from the top of the Triage page.

When a new task enters the Triage inbox:

- **No action**: leave it unassigned and notify no one
- **Notify**: notify the selected people. Inbox items use the type **Triage responsibility**, with the label **This task needs your triage**
- **Assign**: assign new Triage-status tasks to the selected people

This is not the same as Inbox snooze. Inbox snooze hides a personal notification. Snooze in the Triage inbox hides the task in the Space queue.

## Triage rules

Path: Space settings → Triage → Triage rules.

Rules automatically process and route tasks in the Triage status. They are not Space Automations and not Automation workflows.

You can typically:

- Match on status, priority, assignee, creator, Project, labels, task type, due date, created date, content, and similar fields
- Move the task to a Space, set status, assign, label, set a Project, or set priority
- Run multiple rules in order. A later rule overrides conflicting fields from an earlier rule, and the UI marks the conflict
- Disable, move up, move down, or delete a rule. Deletion takes effect immediately and cannot be undone

When a rule moves a task out of the Triage status, the task leaves the Triage inbox.

## Turn the Triage inbox off

Before it turns off, the product warns that current tasks in the Triage status will move to **Backlog**. If a task type has no usable Backlog status, turning it off fails.

After it is off:

- The sidebar entry disappears
- New inbound submissions no longer enter the Triage inbox
- Viewers in a Private Space can no longer create tasks

## Common questions

### Why don't boards or My tasks show work in the Triage status?

Regular task lists and boards exclude the Triage status by default. Review it in the Triage inbox, turn on **Show Triage tasks** in display options, or save a View that includes that status.

### Where does a task go after I accept it?

It moves to the task type's default status and appears in ordinary task lists and boards.

### How is the Triage inbox different from Inbox?

The Triage inbox is a Space queue. Inbox is personal. When responsibility is set to **Notify**, the selected people see the task in both places.

### Why does Accept require a priority?

The Space has **Require explicit prioritization** enabled.

### Why can a Viewer create only Triage-status tasks?

In a Private Space, the Viewer role can submit work for review but cannot push it into the regular workflow. That Space role is not the Organization Guest role. Public Space limits follow the product.

## Related docs

- [Spaces](/docs/space/spaces.md)
- [Tasks](/docs/space/tasks.md)
- [Task statuses](/docs/task/task-statuses.md)
- [People](/docs/space/members.md)
- [Views](/docs/space/views.md)
- [Inbox](/docs/agent-and-computer/inbox.md)
- [Automations](/docs/space/automations.md)
- [Sprints](/docs/space/sprints.md)
- [Jira integration](/docs/integration/jira.md)
- [GitHub integration](/docs/integration/github.md)
