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

# Quickstart

> From signup to your first approved proposal in under ten minutes.

This walkthrough takes you from a fresh workspace to your first agent-drafted action sitting in the Inbox, ready to approve.

<Steps>
  <Step title="Sign in to the cockpit">
    Open [meshpilot.app/login](https://meshpilot.app/login) and sign in with the email your pilot invite was sent to. The cockpit lands on **Home** — your control tower.
  </Step>

  <Step title="Create your first brand">
    Head to **Settings → Workspace**. Add a brand for the storefront you want to operate. A brand is a distinct operating identity — typically one Shopify store with one ad account.

    <Note>
      Brands are the unit of work in Mesh Pilot. Every proposal, every memory, every approval is brand-scoped.
    </Note>
  </Step>

  <Step title="Connect Shopify">
    Open **Settings → Integrations**, find the Shopify card, and click **Connect**. You'll be redirected to Shopify's OAuth consent screen. Pick the store, authorize, and you're back in the cockpit. The card now shows **Connected**.
  </Step>

  <Step title="Connect Meta Ads">
    Same flow. Click **Connect** on the Meta Ads card, pick the ad account you want Mesh Pilot to operate, and authorize. Within a few minutes the Ads agent's hourly poll starts pulling spend, revenue, and campaign state into the cockpit.
  </Step>

  <Step title="Watch the first proposal arrive">
    Open **Inbox**. Once the Ads agent has enough fresh data — usually within an hour — it drafts its first proposal: a pause, a budget shift, a creative rotation, whatever your spend pattern warrants.

    Each proposal shows you the agent's reasoning, the predicted impact, and three actions: **Approve**, **Edit**, or **Reject**.
  </Step>

  <Step title="Approve, and let it run">
    When you approve, the orchestration engine writes the change back to Meta Ads. The action moves to **History**, and the change becomes the canonical update — Meta is the source of truth, the cockpit just shows you what happened.
  </Step>
</Steps>

## What to do next

<CardGroup cols={2}>
  <Card title="Explore Inbox" icon="inbox" href="/cockpit/inbox">
    The single decision queue. Filter, batch-approve, and triage.
  </Card>

  <Card title="Wire up Loops" icon="repeat" href="/cockpit/loops">
    Cross-agent flows like COD confirmation and Ads anomaly response.
  </Card>

  <Card title="Tune autonomy" icon="sliders" href="/cockpit/settings">
    Decide which low-risk actions can fire without your explicit approval.
  </Card>

  <Card title="Connect more platforms" icon="plug" href="/integrations/overview">
    Google Ads, TikTok, HubSpot, LiveKit, and more.
  </Card>
</CardGroup>