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

# Workspace overview

> Understand how Suppio workspaces, agents, settings, and deployment tabs fit together.

The dashboard is organized around workspaces and agents.

A workspace holds billing, usage, website URL, workspace information, and agents. Each agent holds context, sandbox testing controls, and deployments. Discord-specific routing and behavior settings remain grouped under **Discord** after an agent is connected to a server.

## Main areas

<Columns cols={2}>
  <Card icon="layout-dashboard" title="Workspace">
    Manage workspace name, website URL, workspace information, logo, billing, and agents.
  </Card>

  <Card icon="bot" title="Agent">
    Manage context, sandbox testing, deployment, and logs for one support agent.
  </Card>

  <Card icon="rocket" title="Deploy">
    Set up Discord, chat widget, support page, or API. Active web and API methods become direct sidebar tabs.
  </Card>

  <Card icon="chart-column" title="Usage">
    Review credits, conversations, and all usage events.
  </Card>
</Columns>

## Recommended setup order

1. Create the workspace.
2. Create an agent.
3. Add workspace information.
4. Add context.
5. Test in the sandbox and choose the intelligence level for test messages.
6. Configure Discord behavior if you are deploying to a Discord server.
7. Deploy to the surface your users need.
8. Open the live deployment from its sidebar tab when you need to edit it.
9. Review usage, analytics, and knowledge gaps after launch.

## Workspace information

Workspace information is a short grounding summary for the support agent. It should describe what the workspace supports, who the users are, and what kinds of help the agent should provide.

Good workspace information helps Suppio understand your product or community before it searches detailed context.

Workspace information is not a replacement for context. Deployment methods remain unavailable until the agent has at least one active context source.

## Agent sandbox

Use the sandbox before launching. Ask questions that real users ask and verify:

* the answer is accurate
* the tone is right
* missing context is easy to identify
* escalation behavior matches your expectations

## Related pages

<CardGroup cols={2}>
  <Card title="Context" icon="database" href="/context">
    Add knowledge sources to the agent.
  </Card>

  <Card title="Deployment" icon="rocket" href="/discord">
    Choose where users can talk to the agent.
  </Card>
</CardGroup>