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

# Product surfaces

> Where teams configure Dubot and where customers experience it

## Authoring application

The current Dubot application groups workspace authoring in the sidebar. This navigation helps
teams find editors, but it is not the dependency order of the product.

| Area         | What teams manage                                                               |
| ------------ | ------------------------------------------------------------------------------- |
| Overview     | Workspace usage, outcomes, action health, Guidance, and token spend             |
| Build        | Wizards, Guidance, Resource Center, Capabilities, Actions, Knowledge, and Brand |
| Integrations | MCP connections and configuration                                               |
| Configure    | Product Crawler, Team, and Workspace settings                                   |

Conceptually, knowledge and actions are workspace resources. Capabilities package those resources
with reusable instructions. Wizards and the Resource Center Agent consume capabilities to create
customer-facing experiences. Guidance is governed separately and can be launched from those
experiences.

## Choose a customer surface

| Surface         | Choose it for                                                                | Configuration model                                                                   |
| --------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Resource Center | A page-aware destination for browsing, Search, Ask, and explicit next steps  | One versioned Resource Center per workspace                                           |
| Wizard          | A focused conversational job in a specific part of the product               | One placement per Wizard; create additional Wizards for other placements or targeting |
| Guidance        | A reviewed walkthrough or a constrained goal completed against the live page | One workspace Guidance configuration with separately versioned guides                 |
| Action toast    | Status, confirmation, and outcomes for the end-user MCP action channel       | Appears only when that controlled-rollout channel requests an action                  |

## Browser SDK

The browser SDK provides four distinct end-user surfaces.

<CardGroup cols={2}>
  <Card title="Resource Center" icon="library" href="/product/resource-center">
    A page-aware support destination with curated cards, Help Center search, Ask, and launches
    into reviewed guides or host actions.
  </Card>

  <Card title="Wizard" icon="message-circle" href="/product/wizards">
    Conversational help rendered as a bubble, inline surface, sidebar, or fullscreen experience.
  </Card>

  <Card title="Guidance" icon="mouse-pointer-click" href="/product/guidance">
    A visible overlay that can explain, indicate, ask, and perform reviewed steps in the product.
  </Card>

  <Card title="Action toast" icon="bell" href="/integrations/mcp#end-user-action-channel">
    Status, approval, and outcome feedback for actions requested through the end-user MCP channel.
  </Card>
</CardGroup>

## MCP surfaces

Dubot exposes separate MCP services for separate audiences:

* public documentation search;
* authenticated workspace authoring;
* controlled-rollout end-user actions through a live, signed-in product tab.

They have different hosts, credentials, tool catalogs, and consent boundaries. See
[MCP servers](/integrations/mcp) before connecting a client.

<Note>
  Screenshots highlight implemented UI states. Workspace configuration determines the final
  customer experience.
</Note>