Team Triage settings

Open Team Settings → Triage to control intake for an accessible Team.

Team settings and Team Issue work are separate permissions. A workspace administrator may have governance access to settings without receiving the Triage queue, processing actions, archive actions, or Issue editing. Public-Team readability also does not grant either settings or Triage operations.

The page shows a Team's Triage settings only to members of that Team. If the settings cannot be read (for example, a workspace administrator outside the Team, or a failed request), the page says Triage settings could not be loaded and offers Retry instead of showing switches, so nobody changes a configuration they cannot see.

Enable Team Triage

The Enable Triage for this Team switch requires the Team's Team Settings Management permission. The change appears immediately, rolls back if saving fails, and is confirmed after the server accepts it.

Require explicit prioritization

The Require explicit prioritization switch is available after Triage is enabled. When selected, Issues must have a priority before they can be moved out of Triage. This setting uses the same immediate update, rollback, and save confirmation behavior.

When disabled:

• The Team sidebar does not show Triage or its count.
• The explicit prioritization setting remains visible but disabled.
• Accept agent submissions is off and disabled.
• Explicit Triage creation is rejected with a friendly error.
• Normal authorized Team Issue creation continues through the existing workflow.

New Teams start with Triage disabled.

Accept agent submissions

The Accept agent submissions switch decides whether agents connected to Integrity can file Issues into this Team's Triage inbox. Each agent submission waits in Triage like any other intake until someone accepts, rejects, snoozes, or marks it as a duplicate.

The setting is on by default once Triage is enabled. While Triage is off, the switch is off and disabled with the note Turn on Triage to accept agent submissions; enabling Triage again restores the previous choice. Changing the setting requires the Team's Team Settings Management permission. Without it, the switch is disabled and its note names that permission. The row dims while the change saves, and the switch shows the new value once the server has accepted it.

Turning the setting off refuses new agent submissions. Items already in Triage stay there, and Issues that an agent creates directly in the Team's workflow are not affected. The Team's audit log records each change with its old and new value.

Publish the Team queue view

Open the Team's Triage queue and adjust its filters or Display controls. Local changes apply immediately and remain a private browser draft. A dot on Display indicates that the current filters, ordering, direction, or visible properties differ from the Team default.

Open Display and select Set default for everyone to publish the queue's filters—including its Triage state selection—together with ordering and visible properties. Select Reset to discard the private draft and restore the current server state. Publishing requires the Team's Team Settings Management permission and updates other open sessions through private realtime synchronization.

Triage responsibility

Add current Team members who should receive new and reawakened intake updates. One responsible member can be the static auto-assignee. Team editors retain processing access even when they are not in the responsibility roster.

Ordered automation

Triage automation is currently unavailable. The settings page keeps a disabled placeholder for this planned capability. Core Triage intake, responsibility, snooze/wake, and manual disposition remain available.