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

# Signals

> Signals are what your scouts found — a queue of things that need your attention, ranked by priority, with the evidence behind each one and a way to act on it.

Signals is the queue your [scouts](/ai/scouts) fill. Every Signal is one thing worth your attention — an unanswered thread, a relationship going quiet — with a priority, the evidence it was built from, and the actions you can take without leaving the page.

## The queue

Open **Signals** from the sidebar (or press <kbd>g</kbd> then <kbd>s</kbd>). The sidebar badge counts what is in **New**.

Signals are grouped into four tabs:

| Tab                | What is in it                                                                                                                  |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
| **New**            | Found by a scout and not yet turned into a task or closed. Claiming a Signal keeps it here, marked **You're on it**.           |
| **Waiting on you** | Signals where Orbis needs something from you before it can go further. Today's scouts never ask, so this tab is usually empty. |
| **In progress**    | Signals that became a task                                                                                                     |
| **Done**           | Marked done, or dismissed                                                                                                      |

Every Signal carries a priority: **Urgent**, **This week**, **This month** or **FYI**. Filter by priority with the picker above the list. A fifth, lowest tier has no name and is hidden until you switch on **Show low-priority Signals**.

Until a scout has run, the page shows only **No Signals yet** and a button to set up a scout.

## Reading a Signal

Click a Signal to open it beside the list:

* **Why this priority** — one line explaining the ranking, naming the facts it rests on (for example how many days someone has waited) and where they came from.
* **Evidence** — what the scout saw, with **Open in Inbox** for a thread or **Open link** for a page. Only web links are shown as links.
* **View task** — once a Signal has become a task, a link to it.

## Acting on a Signal

| Action             | What happens                                                                                                                                                   |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **I'll handle it** | Marks you as the owner. The Signal stays in **New** with a **You're on it** badge so your team can see it is covered.                                          |
| **Create task**    | Creates a task from the Signal on your default board (use the arrow beside the button to pick another), links the two, and moves the Signal to **In progress** |
| **Mark done**      | Moves the Signal to **Done**                                                                                                                                   |
| **Dismiss**        | Moves it to **Done** with a reason — wrong priority, duplicate, not relevant, wrong owner, or a factual error. A dismissed Signal cannot be reopened.          |
| **Reopen**         | Brings a Signal you marked done back to **New**                                                                                                                |
| **I've answered**  | On a Signal in **Waiting on you**, sends it back to **New**                                                                                                    |

Each action confirms with a short message; where it makes sense the message offers **Undo**.

<Tip>
  Dismissal reasons are not just bookkeeping — they are how Orbis learns which findings are not worth your time.
</Tip>

## Where Signals come from

Each scout run records what it found; the same thread found again tomorrow updates yesterday's Signal rather than creating a second one. A notification, **A scout found something**, goes to the person who switched the scout on and links straight to the Signal.

Signals inherit their scope from the scout: a scout watching **Your accounts** produces Signals only you can see; one watching **The whole organisation** produces Signals your whole team can see and act on.