> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sreagent.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Control Tower tickets and multi-organization view

> How critical findings open tickets automatically, and how to review findings across all your organizations.

export const Plan = ({tier}) => <Badge color="blue">{tier} plan</Badge>;

These are the details behind the [Control Tower](/guides/prevent/control-tower) page.

<Plan tier="Business" />

## Automatic tickets for critical findings

When a run detects a finding at critical severity, it opens one urgent ticket on your ops board, titled `[Overseer] <finding title>`, with the severity, kind, summary, recommended action and a link back to the Control Tower. Evidence items, such as each unresolved secret, are listed with where they were found.

* The ticket links to the finding and to every related alert and investigation.
* A ticket opens only when a finding enters critical: it is new, its severity rises, or it returns after being resolved. A finding that merely stays critical opens nothing.
* There is one ticket per finding. Later runs add new links and update the evidence list, unless somebody has edited the description, in which case your edit is kept and the activity says the evidence changed.
* A finding that returns puts its done or archived ticket back in Triage and adds a "critical again" entry.
* Findings the agent files itself, and dismissed findings, never open a ticket on their own.

Turn this off with **Open a ticket for each critical finding** in the Settings card. It needs a plan that includes the ops board.

## See all your organizations at once

If you belong to more than one organization, you also get an all-organizations view at `/overseer/all`. It merges the findings feed from every organization on a plan with the Control Tower, with each row badged by organization. You can filter and dismiss there. Applying, drafting runbooks, creating fix pull requests and filing tickets need the organization's own page.

## Related

* [Track work on the ops board](/guides/respond/ops-board): the board these tickets land on.
* [Run parent and child organizations](/guides/administer/parent-and-child-organizations): organizations that belong together.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.