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

# Statuses and what they mean

> Look up each status word, mark, and notification event that Squad shows, and what it means.

This page lists the status words, marks, and events that the dashboard shows. The words are quoted as they appear on screen.

The dashboard shows a word only when something is not in its normal state. A finished run, a routine that is on, or a connected bot carries no word. Orange marks what needs you. A blue dot marks something new that you have not read.

## Tasks

### Columns on Tasks

**Tasks** has four columns. Each task is in one column, based on its status. A column shows its name and how many tasks it holds.

| Column | Meaning |
| - | - |
| **Not started** | No teammate has started the task yet. A task with an owner waits here until the owner starts it. A task with no owner waits here until a teammate picks it up. |
| **Needs you** | The task waits on you, or it is blocked. The column has an orange dot. |
| **Working on it** | A teammate picked up the task, is working on it, or is reviewing it. A task whose open questions are all for other people is here too, with "Waiting on" and their names. So is a task whose question you set for later, with "Set for later. Back" and when it comes back. |
| **Done** | The task is finished. **Archived** and **Trash** are under this column. |

A task moves to **Needs you** when a teammate asks you a question on it. When the teammate asks another person, the task is in that person's **Needs you**, and in **Working on it** for everyone else. See [Questions for one person](https://squad.so/docs/tickets.md#questions-for-one-person). When you answer every question, the task goes back to **Working on it** and the teammate continues. See [Answer what needs you](https://squad.so/docs/tickets.md).

### Marks on a task

| Mark | Where | Meaning |
| - | - | - |
| **Urgent**, with an orange dot | Card and task page | The task's priority is urgent. Other priorities are not marked on the card or the task page. |
| **Urgent**, **High**, **Normal**, **Low** | The priority picker, rows in **Archived** and **Trash**, and the **Task created** card in chat | The task's priority. New tasks are **Normal**. |
| **Stuck for N days · no progress** | Card | A teammate's task in **Working on it**, or assigned in **Not started**, has had no update for more than 2 days. Never on a person's own task or an ongoing task. |
| **Ongoing** | Card | The task runs continuously. It never gets the Stuck mark, and stall detection skips it. |
| **Needs you**, with an orange dot | Task page | The task is blocked, and no question is open on it. A visitor of the public dashboard sees **Waiting on the owner**. |
| **This task needs you** | Task page | A heading over the question that waits on you. Answer it there. |
| **You set this for later** | Task page | A heading over a question that you set for later, with when it comes back and **Bring back now**. You can still answer it. See [Set a question for later](https://squad.so/docs/tickets.md#set-a-question-for-later). |
| "Set for later. Back" and a time, for example "Set for later. Back tomorrow at 9:00 AM" | Card | You set the task's question for later. The task is in **Working on it** for you until the question comes back. On Squad for Mac, the card says "You set its question for later." and when it comes back. |
| "Waiting on" and a name, for example "Waiting on Dana Reyes" | Card, task page, and question | The open questions are for another person. They wait in that person's **Needs you**. Two people: "Waiting on Dana Reyes and Sam Ortiz". See [Questions for one person](https://squad.so/docs/tickets.md#questions-for-one-person). |
| **Unassigned**, **Waiting for pickup** | Task page | No teammate owns the task yet. The two words show together under **Owned by**. |
| "\[name] hasn't seen this yet." | Task page, under a comment | A teammate that the comment notified has not seen it yet. Each teammate is named once, under the newest comment that it has not seen. Two teammates: "\[name] and \[name] haven't seen this yet." More: "\[name] and \[n] others haven't seen this yet." See [Steer a task with a comment](https://squad.so/docs/missions.md#steer-a-task-with-a-comment). |

Archived tasks and tasks in Trash are not in the columns. See [Track work on Tasks](https://squad.so/docs/missions.md).

## Questions

A question is open until every part of it has an answer. Open questions wait in **Needs you**, and the first ones show on **Today**. A question that you set for later waits under the line for later until it comes back. See [Set a question for later](https://squad.so/docs/tickets.md#set-a-question-for-later).

| Label | Where | Meaning |
| - | - | - |
| **Over a day** | A question or an email in **Needs you** | It has waited on you for more than a day. |
| **All (N)**, **Over a day (N)**, **Over 30 days (N)** | Filters in **Needs you** | The counts include questions and emails. **Over 30 days** shows only when something has waited that long. |
| "1 question for later", or "N questions for later" | **Today** and **Needs you** | The questions that you set for later. Select the line to list them. |
| "Back" and a time, for example "Back tomorrow at 9:00 AM" | A question that you set for later | When it comes back to your **Needs you**. On Squad for Mac and Squad for iPhone and iPad with a 12-hour clock, a time on the hour has no minutes, for example "Back tomorrow at 9 AM". |
| **For later** | **Needs you** on Squad for Mac, and a page on iPhone and iPad | The list of the questions that you set for later. On the Mac, an open one says "You set this for later." and when it comes back. |
| **Urgent** | A question in **Needs you** | The question's task is urgent. No other priority is marked. |
| **All answered** | Question card | Every part of the question has an answer. Answered questions are under **Resolved** in **Needs you**. |
| **Waiting on you, nothing asked yet (N)** | **Needs you** | Tasks that wait on you, but the teammate did not ask a question. |
| **Purchases to approve** | **Needs you** | Payments that teammates want to make with your card. See [Purchases](#purchases). |

### Answers on a question

A question shows the buttons that fit what the teammate asks. The question card looks the same on **Today**, in **Needs you**, on the task page, and in chat.

| The teammate asks for | Buttons | What the teammate gets |
| - | - | - |
| An approval | **Approve**, **Request changes** | **✓ Approved**, or **↩ Changes requested:** and your text |
| A yes or no | **Approve**, **Decline**, **Something else…** | **✓ Approved**, **✕ Declined**, or your own words |
| A choice | One numbered row for each option, then **Something else…** | **✓** and the option, or your own words |
| Access | **Connect** and the app's name (**Open Custom integrations** when no app is named), **Mark granted**, **Something else…** | **✓ Access granted** |
| An action | **I’ve done this**, **Something else…** | **✓ Done** |
| Information | A text box and **Send answer** | Your text, or **✓ Input provided** |

Questions also have **Skip**, which tells the teammate "✕ Skipped: not needed, carry on without it". Only the owner answers a question for access or an action, unless the teammate asked one person. Then that person and Administrators can answer it too. On an access or action question for no one in particular, other people see the request and "asked the squad’s owner for this, so the owner marks it done", with no buttons. A question for another person says "Waiting on" and the name, and keeps its buttons only for the people who can answer it. **Ask someone else** passes it to another person. See [Ask someone else](https://squad.so/docs/tickets.md#ask-someone-else). **Discuss with** and the teammate's name opens the question's own conversation.

An answered part folds to one line with your answer, **Show request**, and **Undo**. **Undo** opens the part again and puts the task back in **Needs you**. After you answer on **Today** or in **Needs you**, **Just answered** keeps **Undo** for 45 seconds.

People other than the one who answered see a short label: **Approved**, **Declined**, **Changes requested**, **Marked granted**, **Done**, **Answered**, **Skipped**, or **Answered in chat**. A question that closed with its task shows **Canceled**.

## Teammates

### State on a teammate's face

A teammate's face shows its state. Screen readers say the state in words.

| Mark | Meaning |
| - | - |
| A dot that circles the face | The teammate has a run in progress. |
| An ember dot on the face | The teammate needs something from you: it reports a problem, one of its tasks waits on you or is blocked, or it has email drafts or escalations for you. |
| Closed eyes, on the teammate's page | The teammate is paused. In the sidebar, the gray line says so. |
| A blue dot at the end of the sidebar row | A reply that you have not read. |

With **Animated teammates** off in **Settings** > **You**, the faces stay still. On a shared public view, visitors see **Waiting** where you see **Needs you**.

A teammate's **About** says its state in a sentence, for example "Otis is working on 2 tasks and has finished 1 today." When something waits for you, it adds how many drafts and questions, with **Open Needs you**.

### Notices on a teammate's page

| Notice | Meaning |
| - | - |
| **Paused by** and a name, **Paused** and a reason, or **Paused** | The person or teammate named paused the teammate: you, an Administrator, your chief of staff, or the teammate itself. An older pause shows only **Paused**. **Resume** starts it again and gives it the @mentions, task assignments, and emails that waited. |
| The teammate's name, **needs attention.**, and a reason | The teammate reported a problem. |

A paused teammate does not run from the dashboard. Its routines are off, chat messages to it are refused, and @mentions, task assignments, and emails wait until you resume it. See [Add, change, and pause teammates](https://squad.so/docs/agents.md#pause-a-teammate).

### Line in the sidebar

Under each name in the sidebar, a gray line shows what the teammate is doing.

| Line | Meaning |
| - | - |
| A sentence about the current work, or **Working on** and a task | The teammate is running and reported what it is doing. |
| "Working on" and up to two helpers' names (with "and more" when more helpers work), then "with a helper" or "with helpers". "Working with a helper" or "Working with helpers" when no name can show. | The teammate's helpers work on part of its job, and they started after the teammate last reported what it is doing. When the helpers are done, the teammate's own line comes back. On Squad for Mac, a helper whose name is an order reads as what it is doing, for example "Drafting the summary letter with a helper". See [See the helpers your teammates start](https://squad.so/docs/chat.md#see-the-helpers-your-teammates-start). |
| **Working…** | The teammate is running and has not reported details yet. |
| **Waiting for other work on the cloud computer to finish** | The teammate runs on a Claude Code account, and its run waits for free memory on your squad's computer before it starts. It starts by itself when memory frees up, for example when another Claude Code run ends. See [Limits and defaults](https://squad.so/docs/limits-and-defaults.md#runs). When teammates keep waiting, a banner says so. See [Your cloud computer keeps running low on memory](https://squad.so/docs/agent-stuck.md#your-cloud-computer-keeps-running-low-on-memory). |
| **Needs you**, in orange | The teammate needs something from you. A teammate whose tasks wait only on other people's questions does not show it to you. |
| A reason, such as **Paused by Atlas** | The teammate is paused. |
| **Idle · active Nm ago** | The teammate is idle and was active in the last 7 days. |
| **Idle** | The teammate is idle. |

When the sidebar is collapsed, a teammate's tooltip ends in **needs you** or **working**, and **unread reply** when there is one.

## Chat

### Conversation list

| Mark | Meaning |
| - | - |
| A small spinner | The teammate is working in this conversation. |
| A blue dot and a bold title | A reply that you have not read. |

A conversation with neither has no mark.

### Your messages

| Label | Meaning |
| - | - |
| **Sending…** | Squad is delivering your message to the teammate. |
| **Queued** | The teammate is still replying to an earlier message in this conversation. Your message waits its turn. **Steer now** hands it to the reply in progress. |
| **Steering…** | You selected **Steer now**. Squad hands the message to the run in progress. |
| "Handed to the run in progress. The reply will cover this too." | The run in progress took the message that you steered. Its reply answers both messages. |
| "This message reached the run in progress, but that run stopped before answering it. Check the replies above before sending it again." | On a Claude Code account: the run stopped unexpectedly while your steered message was already in it. Squad does not send it again. It shows **Retry**. When you stopped the run yourself with **Stop**, the message shows the ordinary stopped notice instead. See [Send a message while the teammate is busy](https://squad.so/docs/chat.md#send-a-message-while-the-teammate-is-busy). |
| **Retry** | The message failed. Select it to send the message again. A failure where no reply came says "No reply arrived". |
| **Stopping…** | You or an Administrator selected **Stop**. The run ends soon. See [Stop a reply in progress](https://squad.so/docs/chat.md#stop-a-reply-in-progress). |
| "This run was stopped before the agent replied. Anything it already saved stays." | The run was stopped before the teammate replied. This is not a failure, so there is no **Retry**. |
| A version number such as **1/2**, between arrows | You or another person edited this message. The numbers show which version of the conversation is on screen. See [Copy, fork, or edit messages](https://squad.so/docs/chat.md#copy-fork-or-edit-messages). |

### Card headers in chat

Teammates post these cards in chat. Each header tells you what the card wants. A card that asks something of you is orange only for the person who can answer it.

| Header | Meaning |
| - | - |
| The teammate's name and the task | A question. Answer it on the card, on **Today**, or in **Needs you**. |
| **All answered** | Every part of the question has an answer. |
| **Paused for your answer** | The teammate waits for you to pick an option. |
| **A key to add** | The teammate needs a key or other secret value. |
| **An app connection to add** | The teammate proposes an MCP server to add. |
| **Connect** and the app name | The teammate asks you to connect an app. |
| **Your computer needs you** | The teammate asks you to take over its computer. |
| **Task created** | The teammate created a task from the conversation. The card shows its priority and its owner. |
| **Form to fill** | The teammate asks you to fill in a form on a web page. See [Form cards](#form-cards). |
| **Add a card to your Wallet**, or a purchase state such as **Waiting for your approval** | The teammate asks you to add a card, or wants to pay with one. See [Purchases](#purchases). |

After you act on a card, it shows what happened, for example **✓ saved to the vault**, **✓ added**, or **Answered** and the time, followed by **· sent to the teammate**. For how to use each card, see [Chat with your teammates](https://squad.so/docs/chat.md).

### Helpers in chat

When a teammate starts helpers, the conversation shows one line, for example "Asked 3 helpers to check the evidence". These words show with it:

| Words | Meaning |
| - | - |
| "Working on Docs audit with a helper", "Working on Pricing research, Docs audit and more with helpers", "Working with a helper", "Working with helpers" | The teammate's working message and its line in the sidebar: what its helpers work on now. Up to two names, never a count. On Squad for Mac, the working message right under the helpers line says "Working on it" instead. |
| A sentence such as "2 ran out of time." or "Docs audit didn't report back." | A helper did not finish as asked. |
| "It stopped on a sign-in problem.", "It ran out of time.", "It ran out of room before it finished.", "It hit a usage limit.", "It was stopped.", "It stopped before it finished." | Why a helper failed, when Squad knows. |

For each helper's run, open **History**. See [See the helpers your teammates start](https://squad.so/docs/chat.md#see-the-helpers-your-teammates-start).

### Form cards

| Label | Meaning |
| - | - |
| **Form to fill** | The teammate waits for your values. **Fill the form** sends them. **I can't fill this** declines. |
| **Submitted** | Your values reached your squad's computer. The teammate is filling the page now. |
| **Tell my teammate** | Your values arrived, but the teammate was not told yet. Select it to tell the teammate. |
| **Filled** | The form on the page was filled with your values. |
| **Not filled** | The page could not be filled. Ask the teammate to send the form again. |
| **Declined** | You declined. The teammate finds another way. |
| **Expired** | The request lapsed. Ask the teammate to send it again. |
| **Dismissed** | The card was dismissed. |

See [Fill a form that a teammate sends you](https://squad.so/docs/form-cards.md).

## History

### Marks on a run

**History** marks only a run that is still going or did not finish. A finished run carries no mark. Its details say **Finished**.

| Mark | Meaning |
| - | - |
| **Running** | The run is in progress. |
| **Stopped** | You or an Administrator stopped the run with **Stop**. This is not counted as a failure. See [Stop a run](https://squad.so/docs/runs-and-health.md#stop-a-run). |
| **Still finishing** | The run stopped sending events, and no end signal arrived. If the run reports back, the row corrects itself. This is not counted as a failure. |
| **Interrupted** | A restart of your squad's computer cut the run off, a short AI provider error stopped it and Squad retried it, or the run failed and the teammate's next attempt is still working on it. This is not counted as a failure. |
| **Picked up** | The run failed, and the teammate's next attempt in the same turn finished the work. This is not counted as a failure, and **Health** does not list it. On Squad for Mac, the row says **Picked back up**. |
| **Replaced** | A newer run took over from this one. This is not counted as a failure. |
| **Reported twice** | The run was reported twice. The other entry shows how it went. This is not counted as a failure. |
| **Didn’t finish** | The run ended with an error or ran out of time. This includes a run that your AI provider refused. |

On Squad for Mac, a run that ran out of time shows **Ran out of time** in its row, not **Didn’t finish**. See [See what your squad did](https://squad.so/docs/runs-and-health.md#on-squad-for-mac).

### Kinds of run

| Kind | What started the run |
| - | - |
| **Scheduled run** | A routine, including a heartbeat. |
| **Chat** | A message that you or another person sent to the teammate. |
| **Telegram or a mention** | A Telegram message, or a wake such as a nudge or an @mention from you or another teammate. |
| **Email** | An email that arrived in the teammate's inbox. |
| **Research** | A research tool call. |
| **App** | A system task, such as a memory recall. |
| **Tool** | A single tool call. Tool runs are hidden until you turn on **Tools** in the **Kind** filter. |
| **Helper** | A helper that another run started. Its title is "Helper:" and the helper's short name, or "Helper run" when there is no name to show. See [See helper runs](https://squad.so/docs/runs-and-health.md#see-helper-runs). |
| **Trigger** | An event that a trigger received. See [Triggers](https://squad.so/docs/triggers.md#what-a-trigger-run-looks-like). |

The **Kind** filter names them **Routines**, **Chats**, **Telegram and mentions**, **Emails**, **Research**, **Apps**, **Tools**, **Helpers**, and **Triggers**.

### Notes on a run

| Note | Meaning |
| - | - |
| "A restart cut this run short, and Squad picked it back up." | A restart interrupted the run, and Squad gave the work back to the teammate: a chat message in the dashboard, work on a task, a request, a reply in a chat app, or a routine's run. The teammate continued in a new run. See [Interrupted runs](https://squad.so/docs/agent-stuck.md#interrupted-runs). |
| "The AI service hiccuped, and Squad picked this run back up." | A short AI provider error stopped the run, and Squad retried it. |
| "Cut short by maintenance, and not run again." | A restart cut the run off, and Squad did not run it again. Check that its work finished. |
| "Your teammate picked this back up and finished it." | The run failed, and the teammate's next attempt in the same turn finished the work, for example on a model under **When it can’t answer**. The run is marked **Picked up**. It does not count as work that did not finish, and **Health** does not list it. |
| "Your teammate is trying this again." | The run failed, and the teammate's next attempt in the same turn is still working. |
| "A newer run took over from this one." | A newer run took over, and the run is marked **Replaced**. In the list, the row says "Replaced by a newer run." |
| **Reported twice** | "This run was reported twice. The other entry shows how it went." In the list, the row says "Reported twice." |
| **Ran out of time** | The run reached a time limit that is left from an earlier setting. **Check the time limit** opens that limit in the teammate's setup. See [Time limits](https://squad.so/docs/agent-stuck.md#time-limits). |
| **Didn't finish** and a plain sentence | The run ended with an error. The error text from the system is under **Technical details**. |

For how long a run can stay silent, see [Limits and defaults](https://squad.so/docs/limits-and-defaults.md#runs).

When a Claude Code account reaches its usage limit during a run, Squad switches to your next Claude Code account. The run continues once on the new account. If it had already done work, the teammate is told to continue from where it stopped and not to repeat what is done. If the next account has reached its limit too, the run fails. When every Claude Code account has reached its limit, Claude Code cannot serve runs until one resets, and runs move to the next model in **When it can’t answer** if you set one. A line above every screen then says "Claude Code has reached its usage limit." and when your teammates pick up again. See [Claude Code reached its usage limit](https://squad.so/docs/agent-stuck.md#claude-code-reached-its-usage-limit). For History and Health, see [See what your squad did](https://squad.so/docs/runs-and-health.md).

### Health

Only the owner and Administrators see **Health**.

| Section | Meaning |
| - | - |
| **All clear** | No failed or interrupted runs today, and no provider limits in effect. It does not show while the line "Claude Code has reached its usage limit." is above the screen. Then, with no failed or interrupted runs and no provider limiting your teammates, **Health** says "No failed or interrupted runs today. Only the usage limit above is holding your teammates up." |
| **Provider status** | An AI provider is rate-limiting your teammates, and recent runs failed. Squad does not repeat a run that failed on a rate limit. New runs work again when the provider accepts calls. |
| **Needs a look (N)** | Runs that failed today. **View in History** opens one in History. |
| **Routine interruptions (N)** | Runs marked **Interrupted** today, including failed attempts that the teammate is still trying again. Runs marked **Picked up**, **Replaced**, or **Reported twice** are not listed. Each row is tagged **resumed** or **not run again**. Check that the work of runs tagged **not run again** finished. |

## Routines

A routine that is on has no label. Its switch shows whether it is on.

| Label | Where | Meaning |
| - | - | - |
| The switch, off, and a gray name | Routines list | The routine is paused. |
| "It can’t run as it’s set up: it reminds in the background while background reminders are off." and **Fix it** | Routines list | The routine is set to run as a background reminder while background reminders are off for the teammate, so it is skipped every time. **Fix it** opens the teammate's setup. Such a routine comes first in its teammate's group. |
| An error and **See what happened** | Routines list | The last run failed. **See what happened** opens that run in History. |
| **All routines**, **On**, **Paused**, **Can’t run** | **Filter** on Routines | Shows routines by state. **Can’t run** shows the routines that cannot run as they are set up. |

When a change to a routine fails, the message says why. It starts with "Your cloud computer did not create the task.", "did not update the task.", "did not start the task.", or "did not move the task to that agent." and then gives the computer's own reason. When the connection to the computer was lost, the message says that Squad cannot tell whether the change went through, and asks you to check the list, or History, before you try again. See [Schedule recurring work with routines](https://squad.so/docs/scheduled.md).

## Triggers

### Trigger labels

A trigger's page shows one of these labels. On **Routines**, under **When something happens**, a trigger has a switch, and a note only while it waits for something.

| Label | Meaning |
| - | - |
| **On** | The trigger wakes its teammate when events arrive. |
| **Paused** | The trigger is off and wakes no one. A webhook trigger still keeps the events that arrive. An app event trigger usually gets no events while it is paused. The page says why when Squad paused it. |
| **Suggested** | A teammate suggested the trigger. It does nothing until the owner or an Administrator turns it on. On **Routines**, the note says "\[name] suggests this. It stays off until it’s turned on." Its page shows no status next to the name. |
| **Connecting** | Squad is asking the app to send this event. This usually takes a few seconds. On **Routines**, the note says that it waits for the app to confirm that it listens. |
| **Needs a secret** | The sender is **Stripe**, **Shopify**, or **Standard Webhooks**, and no secret is saved. Squad refuses every request until you add it. On **Routines**, the note says that it waits for its signing secret. |

### Event outcomes

These words show next to each event under **Latest events** on a trigger's page.

| Outcome | Meaning |
| - | - |
| "Waiting to send" | The event waits for the trigger's current run to end. |
| "Waking the teammate" | Squad is sending the event to the teammate. |
| "Retrying (attempt N)" | The last try to wake the teammate failed. Squad tries again. |
| "Held while the teammate is paused" | The teammate is paused. Squad sends the event when you resume the teammate. |
| "Teammate woken, run starting" | The teammate got the event, and its run is starting. |
| "Teammate working" | The teammate's run is going. |
| "Done" | The run finished. |
| "Run stopped" | Someone stopped the run. This is not a failure. |
| "Run failed", "Run timed out", or "Run ended:" and a status | The run did not finish its work. **Retry** sends the events again. |
| "Teammate woken, no run started" | The teammate got the event, but no run started. **Retry** sends it again. |
| "Could not wake the teammate" | Every try to wake the teammate failed. The error shows under the event. **Retry** sends it again. |
| "Not run: the trigger was paused" | The event arrived while the trigger was off. Turn the trigger on, and **Run now** runs it. |
| "Not run: the daily limit was reached" | The trigger had started as many runs that day as **Most runs per day** allows. **Run now** runs it. |
| "Not run: the teammate was removed" | The trigger's teammate was removed. |
| **Test** | A tag on an event that someone sent with **Send test event**. |

**Run now** and **Retry** show only while the trigger is on, and only to people who can change triggers.

## AI accounts

On **Settings** > **AI**, an account shows a status word only when it matters.

| Status word | Meaning |
| - | - |
| **Signed out** | The provider signed this account out. Select **Reconnect** to sign in again. |
| **Expired** | The sign-in has expired. Select **Reconnect** to sign in again. |
| **At its limit** | "This account has used up its limit for now, so your squad can't use it until the limit resets." |
| **Out of date for some teammates** | "Some teammates hold an older copy of this account. Update them at the top of the page." |
| **In use** | Your squad uses this one first. Shows only when the card has other accounts. |

Other labels on **Settings** > **AI**:

| Label | Meaning |
| - | - |
| **Hit its limit, cooling down** | A recent run on this provider hit a rate limit. |
| "Your squad is using \[name] meanwhile" | Shows above that account when the accounts above it can't be used right now. |
| "None of these can be used right now, so your squad uses its next AI." | No account on this provider can serve runs, so runs move to the next model under **When it can’t answer**. |
| A banner that says the provider "is signed out on your squad" | Runs that use it fail until you reconnect it. **Today** and **Needs you** also say so first. Everyone in your squad sees this. Only the owner and Administrators get **Reconnect** with the provider's name. |
| "\[account] is signed out, so your squad can’t work.", in a banner above every screen | Claude Code is signed out, or every ChatGPT account has expired, and your squad cannot work until it is reconnected. Everyone in your squad sees it. The owner and Administrators get **Reconnect**. It does not show on **AI**. On **Today** and **Needs you**, it leaves out Claude Code, because the first row there says it. See [An expired AI connection](https://squad.so/docs/agent-stuck.md#an-expired-ai-connection). |
| "Claude Code has reached its usage limit.", in a line above every screen | Every Claude Code account is at its usage limit. The line says when your teammates pick up again. Everyone in your squad sees it. The owner and Administrators who work with every teammate get **Add another account**. It is not a sign-out. See [Claude Code reached its usage limit](https://squad.so/docs/agent-stuck.md#claude-code-reached-its-usage-limit). |
| "Some teammates hold an older copy of an account." | Select **Update them** to update them. Only the owner and Administrators see it. |

## Email

### Messages

| Label | Where | Meaning |
| - | - | - |
| **Draft** | Message in a conversation | The teammate drafted this message for your review. It has not been sent. |
| **Scheduled** | Message and inbox row | The message is set to send later. |
| **Needs you** | Message in a conversation, and inbox row with an orange dot | The teammate asked you to decide how to handle this email. |
| **Bounced** | Message in a conversation and inbox row | The email bounced. The recipient did not get it. The message shows the reason when the provider gives one. |
| **Marked as spam** | Message in a conversation and inbox row | The recipient reported the email as spam. The message says "The recipient marked this email as spam." |
| **Not sent** | Message in a conversation and inbox row | The email did not send. The recipient did not get it. The message shows the reason when the provider gives one. |
| **Draft ready** | Inbox row | A draft waits for your review. |
| A blue dot, **Unread** for screen readers | Inbox row | You have not read the email. |
| A paperclip, **Has files** | Inbox row | The email has files attached. |

A sent message has no label.

### Inboxes

| Label | Where | Meaning |
| - | - | - |
| **This inbox is paused** | **Identity** in the inbox settings | You paused the inbox. Mail still arrives, but the teammate does not read it or send email until you select **Resume inbox**. |
| **Updating…** | Inbox settings | Squad is setting up the inbox or changing its address. |

An inbox that works has no label.

### Custom email domains

| Status | Meaning |
| - | - |
| **Waiting for DNS** | Squad is waiting for the DNS records at your DNS host. |
| **Checking DNS…** | Squad is checking the records now. |
| **Verification failed** | The check failed. The reason is shown next to it. |
| **Connected · DNS verified** | The domain is verified and ready to use. |

Each DNS record also shows **Verified**, **Wrong value**, **Not found yet**, or **Pending**. See [Give a teammate an email inbox](https://squad.so/docs/email.md).

## Apps and channels

| Label | Where | Meaning |
| - | - | - |
| **Connected** | App catalog | You connected at least one account for this app. |
| **Main account** | Account row | Teammates try this account first when they do not pick one. A person's own accounts come before shared accounts. |
| **Shared** | Account row | Everyone in the squad can use the account. A private account shows no tag. See [Who can use an account](https://squad.so/docs/integrations.md#who-can-use-an-account). |
| **Needs reconnecting** | Account row | The app ended the sign-in. The person who connected the account selects **Reconnect**. |
| **Connect** and the app name | Card in chat | A teammate asks you to connect the app. |
| **Connecting · finish sign-in** | Card in chat | The sign-in has started. Finish it in your browser. |
| **Not connected yet** | Card in chat | The app has not confirmed the sign-in. Start it again, or finish it in your browser. See [If the sign-in does not come back](https://squad.so/docs/integrations.md#if-the-sign-in-does-not-come-back). |
| **Connection expired** | Card in chat | The connection expired. **Reconnect in Apps** opens the **Apps** page. |
| **Not connected** | Telegram main bot | Your main Telegram bot is not connected. A connected bot has no label. |
| **Offline** | Each extra Telegram bot, Discord bot, and Slack app | The bot is not running on your squad's computer. A bot that runs has no label. |

**Online** and **Connected** are read only by screen readers, and **Offline** and **Not connected** show, also on Squad for Mac.

## Visible computer

| Label | Meaning |
| - | - |
| **Watching · the squad keeps working** | You are watching the teammate's computer. The teammate keeps control. |
| **You have the keyboard** | You took over. Select **Hand back** to return control to the teammate. |
| **Your computer needs you** | A card in chat. The teammate asks you to take over its computer. |

See [Watch or take over a teammate's computer](https://squad.so/docs/computer.md).

## Docs

A blue dot before a doc's title means that the doc has news for you.

| Tooltip on the dot | Meaning |
| - | - |
| "New. You haven’t opened it yet." | You have not opened this doc yet. |
| "Changed since you last read it." | The doc changed since you last opened it. |

**Mark all as read** on **Docs** clears every dot. Archived docs never show a dot. See [Find and manage your squad's docs](https://squad.so/docs/squad-docs.md).

## Contacts

| Mark | Where | Meaning |
| - | - | - |
| **Do not contact** | A person's row and page, a deal, and a step | Teammates do not email this contact. The person's page says "Do not contact. Your teammates won't email them." and who marked them and when, for example "Marked by Rosa 2 days ago: asked to stop." A deal says "Do not contact \[name]. Your squad's email won't reach them." A step starts with "Do not contact" and the name. See [Mark a contact do not contact](https://squad.so/docs/contacts.md#mark-a-contact-do-not-contact). |
| "today", "tomorrow", "in 3 days", "on 30 Oct" | A step, a follow-up, and a card on a pipeline | When it is due. See [Work a step](https://squad.so/docs/contacts.md#work-a-step). |
| "a day late", "4 days late", in bold | A step, a follow-up, and a card on a pipeline | Its day has passed. Late is said in words. |
| "due yesterday", "due 3 days ago" | A follow-up on a person's page | The follow-up's day has passed. See [Set a follow-up](https://squad.so/docs/contacts.md#set-a-follow-up). |
| "Follow-up not set" | A person's page, when you change a pipeline's card | The person has no follow-up in that pipeline. |
| "No date yet" | **Your move** on **Home** | The step has no day. |
| "promised it", "promised it, in writing", "promised it, signed" | A step | How the step was promised: said, written, or signed. |
| "on it", "waiting for review", "finished", "waiting on someone" | A teammate's step in **Needs you** and on **Today** | Where the teammate's task for the step stands. |
| "working on it", "waiting for review", "finished its task" | A teammate's step on a deal | Where the teammate's task for the step stands. |
| "kept", "missed", "broken", "dropped", struck through | A step on a deal that ended | How the step ended. A done step says nothing more. See [Change a step](https://squad.so/docs/contacts.md#change-a-step). |
| A dot before **Your move** | **Home** | Something of yours is due today or late. |
| A blue dot | **Since you last looked** on **Home** | It changed since your last look. |
| "quiet 16 days", "quiet since yesterday" | **Waiting on them** on **Home** | How long nobody has heard from the deal's people. |
| **Late**, **Yours**, **Your squad's**, **Theirs**, **Nothing next** | The columns of **Deals** | Whose the next step is. **Late** means the time the step was due has passed: a step dated on the dashboard is due at 9:00 on its day. See [Find a deal](https://squad.so/docs/contacts.md#find-a-deal). |
| **A target**, **Quoted**, **On trial**, **Approved**, **Signed**, **Paid** | A deal's money | How sure the money is. Only the owner and Administrators see the amount. |
| "money in", "money out" | A deal | The deal sells or buys. |
| "Closed." with **Won**, **Lost**, or **Dropped** and why | A closed deal | How the deal ended. See [Close, open again, or delete a deal](https://squad.so/docs/contacts.md#close-open-again-or-delete-a-deal). |
| **checked**, **not checked yet**, **Nobody reads it**, **Might bounce**, **Bounced**, **Unsubscribed** | An address on a person's page | Whether the address reaches them. The **Address** filter on **People** says **Checked**, **Not checked yet**, **Nobody reads**, **Might bounce**, **Bounced**, and **Unsubscribed**. See [How email updates contacts](https://squad.so/docs/contacts.md#how-email-updates-contacts). |
| "a weak signal: moves nothing" | A like or a follow in a person's **History** | It counts as a touch but never moves anyone. |
| "1,000 or more" | Counts on **Home** and **Deals** | The count stopped at its cap. See [Limits and defaults](https://squad.so/docs/limits-and-defaults.md#contacts-and-pipelines). |

Pipeline stages are names that you set, so they are not listed here. See [Keep your contacts, deals, and pipelines](https://squad.so/docs/contacts.md).

## Purchases

When a teammate pays with a card, the **Purchase** card in chat and in **Needs you**, and **Purchases** in the **Wallet**, show one of these states. The state is orange only while it waits for your own approval.

| State | Meaning |
| - | - |
| **Getting the checkout ready** | The teammate is preparing the payment. |
| **Waiting for your approval** | You must approve the payment on the device that holds the card. You see **Review and approve**. |
| **Waiting for** and a name | The card's owner must approve the payment on their own device. |
| **Approved** | The payment is approved, and the teammate is placing the order. |
| **Paid** | The order is placed. The card shows the order number when the store showed one. |
| **Declined** | The payment was declined, so nothing was paid. |
| **Not approved in time** | Nobody approved it in time, so nothing was paid. |
| **This store can’t take it** | The store's checkout does not work with an approved card, so nothing was paid. |
| **The store needs a person** | The store asked for a step that only a person can do. The teammate tells you what it needs. |
| **Payment not confirmed** | It is not known whether the payment went through. Look at the card's statement before you try again. |
| **Canceled** | The purchase was canceled, so nothing was paid. |
| **Waiting on your card** | The purchase is on your card, but your role cannot approve it. "Your role in this squad can’t approve payments. Ask the owner to change your role, then approve it." |
| **Stopped** | It stopped before anything was paid. |

A checkout that charges nothing, such as a free trial, only saves the card with the store. Its sentence says "with nothing to pay now", the **Wallet** shows **Nothing to pay now**, and these states use their own words:

| State | Meaning |
| - | - |
| **Waiting for** and a name | The card's owner must approve saving the card on their own device. |
| **Approved** | The card is approved, and the teammate is saving it with the store. |
| **Card saved** | The card is saved with the store, and nothing was paid. |
| **Declined** | The card was declined, so it was not saved. |
| **Waiting on your card** | The card is yours, but your role cannot approve saving it. "Your role in this squad can’t approve saving a card. Ask the owner to change your role, then approve it." |
| **Not confirmed** | It is not known whether the store saved the card. Check your account with the store before you try again. |

See [Let your teammates pay with your card](https://squad.so/docs/payment-cards.md).

## What's new

Each entry in **What's new** has a type label. The filters at the top are **All**, **Features**, **Models**, **Improvements**, and **Fixes**.

| Label | Meaning |
| - | - |
| **New** | A new feature. |
| **Improved** | A change to something that already existed. |
| **Fixed** | A bug fix. |
| **New model** | A new AI model that you can pick. |

## Subscription

| Label | Where | Meaning |
| - | - | - |
| **Active** | Plan card on Billing | Your subscription is active. |
| **Ending** | Plan card on Billing | You canceled. The plan ends on the date shown. |
| **Your subscription is canceled.** and the end date | Banner at the top of the dashboard, and the plan card on Billing | You canceled. Your squad works until the date shown. After that date, your squad and your teammates are scheduled for deletion. |
| **Your subscription is canceled** | Lock screen | The plan has ended, and your squad is locked. |
| **Your subscription is paused** | Lock screen | Your squad is locked while the subscription is paused. |
| **Payment past due** | Lock screen | The latest payment failed, and your squad is locked. |

See [Manage your subscription, credits, and workspace data](https://squad.so/docs/billing.md).

## Notification events

These are the events on **Settings** > **Notifications**. Each has an **In Squad** switch and an **Email** switch. **Not by email** means that the event never sends email.

| Event | Description on screen | In Squad default | Email default |
| - | - | - | - |
| **A teammate needs you on an email** | An email they need you to decide on. | On | On |
| **A reply is ready for you to check** | A teammate drafted an email or a message for you to look at first. | On | Off |
| **A document is ready** | A teammate finished a doc. | On | Off |
| **A task is waiting on you** | Its work stops until you answer. | On | On |
| **A task is done** | A teammate finished a task. | Off | Off |
| **Work failed** | A task or a run hit an error or ran out of time. | Off | Off |
| **A teammate got an email** | It arrived in their inbox, and they handle it. | On | Off |
| **Your week, every Monday** | An email with a link to look back on the week. | Off | On |
| **Billing and credits** | Low credits, renewals and payment problems. Only the owner sees this event. | On | Not by email |
| **A teammate replied to you** | In a conversation you started. | On | Not by email |

When the **In Squad** switch of an event is off, that event does not show in the bell. The bell shows up to 8 of your newest notifications. Reply notifications show only for the conversations that you are in. Selecting a reply notification opens that conversation. A notification about an email, received, drafted, or needing you, opens that email, and a mention opens where it was written. Other notifications open **Activity**. For more, see [Choose your notifications](https://squad.so/docs/notifications.md).


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