Request intake and Triage

One inbox for incoming work

Requests that arrive from outside the studio collect in a project Triage queue instead of becoming untracked chat. Open it from the Tasks header or the sidebar count; it appears for members when something is waiting.

Untrusted by default

A request submitted through a public link or a chat integration is external input. Iterel quarantines its content: it is stored and shown as a report, never executed as an instruction, and rate limits apply at intake. Promoting a request does not trust it — the promoted task carries the report as read-only context and starts with read-only permission.

Promote to a task

From a request, choose a Mission and Priority, then promote. Iterel creates the task in the mission's board lane, preserves the original request as context, and links the two so the queue count drops live. Decline removes a request from the queue without creating work.

Where requests come from

• Request link — a scoped public submission form minted from Project settings.
• Slack — a Send to Iterel message action, the /iterel command, or an @-mention. See Slack intake.
• Linear import — an existing backlog brought in as missions and tasks. See Import from Linear.