Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.warrn.io/llms.txt

Use this file to discover all available pages before exploring further.

Teams have access to the same integration catalog as services. The difference is scope: a team-level integration applies to every service the team owns, unless that service overrides it with its own.

​
Alert sources

You can attach alert sources at the team level when alerts from a source apply to the whole team rather than one specific service. Alerts coming in this way get routed to the team’s on-call. See Integrations for the full catalog and setup details per source. When the same alert source is configured at both team and service level, the service-level config wins for that service.

​
Chat and ticketing

Slack, Jira, and Confluence configured at the team level become the default for every service in the team. Common patterns:
  • A team-wide Slack channel that receives all incident notifications for the team.
  • A Jira project where all action items for the team land by default.
  • A Confluence space the team uses for runbooks.
If a service inside the team needs different routing, set the same integration at the service level - the service-level config takes over for that service. When you add Confluence to a team, the same “Use this space for AI runbook search” toggle is available. With it on, every service the team owns can use that space as a runbook source during AI Triage. Setting it on the team is the easiest way to point one Confluence space at many services without configuring each.