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

# Operate orders in the dashboard

> Place an order, trace its commands and broker outcome, and review the account in Anthid's web app.

The [Anthid dashboard](https://app.anthid.com) uses the same intent, controls, streaming, and ledger services as your API integration. Select the intended organization and paper or live environment before working with an account.

## Connect and configure

Open **Platform > Trading accounts** to link a supported broker account and inspect its connection. Start with paper credentials. Check the broker's supported order types, destinations, and time in force before submission.

Open **Platform > Controls** for account and organization controls, and **Platform > Symbols** for instrument controls. Access depends on your role and plan. Controls gate new creates only; disabling a scope does not cancel resting orders. See [Controls](/pages/controls/overview).

## Submit an instruction

Organization administrators can open **Trade > Order ticket**. Choose the trading account, symbol, side, and supported order specification, then review the request before submitting. API integrations can submit the equivalent `POST /v1/intents` request from the [quickstart](/pages/intro/quickstart).

A successful submission returns an intent ID. It confirms a durable instruction, not a fill.

## Trace the result

| Dashboard area       | What to inspect                                        |
| -------------------- | ------------------------------------------------------ |
| Activity > Intents   | Commands, dispatch state, and intent outcome           |
| Intent detail        | The sequenced create, replace, and cancel action chain |
| Activity > Orders    | Broker order status, filled quantity, and identifiers  |
| Order detail         | The individual order and its related intent            |
| Activity > Positions | Broker-reported holdings, where supported              |
| Streams              | Incoming intent actions, orders, or positions          |

A `SENT` action means the command was handed off. Read the resulting order's status and filled quantity to determine execution. A closed order can be cancelled or filled. A replacement carries a complete order specification and references the original intent ID, not the broker order ID.

The Intents API also exposes refused submissions at `GET /v1/intents/rejections`. These explain authorization, entitlement, and controls refusals before acceptance; they are distinct from a broker rejecting an accepted instruction.

## Review the book

**Analytics > Orders** shows order activity and execution metrics. **Analytics > Exposure** shows holdings valued at broker average cost, rather than current market prices. Ledger queries separate paper and live and are bounded by your plan's history allowance.

Alpaca currently reports orders but not positions through Anthid. An empty Alpaca position view is not evidence of a flat account. See [Broker capabilities](/pages/brokers/overview#broker-capabilities).

After a stream interruption, reconcile the ledger's latest state. Primed subscriptions can rebuild retained orders and positions, but do not replay every missed transition. See [Streaming delivery](/api-reference/stream/overview#initial-state-and-live-delivery).