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

# Dashboard Board

> Understand task status, activity, runtime, notes, and evidence on the board.

# Dashboard Board

The board is the main place to understand work state. It is stronger than chat history for determining whether work is waiting, active, blocked, or done.

## What a task should show

A useful task usually includes:

* Title.
* Status.
* Assignee or responsible agent.
* Priority.
* Summary or source request.
* Acceptance criteria.
* Next action.
* Latest update.
* Attachments, artifacts, or delivery links.

## Common task states

| Status                          | Meaning                                                                                                      |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Inbox**                       | A request exists, but it is not ready to execute yet. It may still need shaping, clarification, or approval. |
| **Drafting spec**               | The work is being clarified into a more executable task shape.                                               |
| **Pending approval / Pending**  | The task is waiting for a user or owner decision before execution should continue.                           |
| **Ready**                       | The task is clear enough and allowed to start.                                                               |
| **In progress / Agent working** | An agent is actively executing the task or subtask.                                                          |
| **Waiting**                     | Work is paused because the task is waiting on input, another step, or an external dependency.                |
| **Blocked**                     | Work cannot continue safely until a real blocker is removed.                                                 |
| **Ready to review**             | Output or evidence exists and needs human review.                                                            |
| **Done / Closed**               | Reviewed and accepted.                                                                                       |

## Waiting vs blocked

This distinction matters:

* **Waiting** usually means the work can continue later after a decision, dependency, or reply.
* **Blocked** means the work cannot safely proceed in its current state.

Examples:

* Waiting for your approval to move forward → usually **Pending approval** or **Waiting**.
* Waiting for a dependency task to finish → usually **Waiting**.
* Missing credentials, broken environment, or failed prerequisite → usually **Blocked**.

<Note>
  If a task is still in Inbox, Drafting spec, or Pending approval, do not assume the agent should already be executing it.
</Note>

## Activity vs Runtime

| Tab          | Meaning                                                                                     |
| ------------ | ------------------------------------------------------------------------------------------- |
| **Activity** | Human-visible updates, edits, notes, status changes, and review comments.                   |
| **Runtime**  | System/orchestration events, dispatches, active assignment updates, and automation details. |

Keeping these separate helps users understand what happened without mixing product updates with internal runtime noise.

## Notes

Task notes can include safe Markdown. Avoid pasting secrets into notes.

## Evidence

Before accepting a task as done, look for the right proof:

* Screenshot or browser proof for UI work.
* Test output for code/API changes.
* Delivery file for user-facing documents or assets.
* Runtime/log evidence for orchestration behavior.
* Clear blocker note if work cannot proceed.