Dashboard Setup

This page is for both developers and non-technical operators who configure Docuworm behavior.

Where setup happens

Use dashboard.docuworm.ai and open Agents. Each agent has five tabs: Settings, Customize, Analytics, Actions, and API Keys.

Settings tab

Use Settings to control core behavior:

• Agent name (what team members see internally)
• Enable page context (whether page content can be included with user prompts)

If page context is enabled in agent settings, the widget can use page content when enable-page-context is active in embed configuration.

Actions tab

Use Actions to define reusable prompts users can trigger in the widget.

Recommended conventions:

• Keep names short and user-facing.
• Make prompts explicit and deterministic.
• Order actions by business priority.

API Keys tab

Use API Keys to create or regenerate access tokens.

Allowed URL rules

Before token creation, add at least one allowed URL.

Production recommendations:

• Add exact origins per environment.
• Include full protocol (http or https).
• For local development, include the exact localhost origin and port you use.

Example set:

• http://localhost:5173
• https://staging.yourdomain.com
• https://app.yourdomain.com

If the widget is loaded from an origin not in the allowed list, authentication is rejected.

Token lifecycle

• Regenerating a token invalidates the previous active token.
• Update deployment secrets immediately after regeneration.
• Keep one active token per agent and rotate deliberately.

Suggested operating model

1. Ops/PM configures agent behavior in dashboard.
2. Engineering embeds widget and maps thread-ref to app entities.
3. Engineering injects runtime context via uploads and addSources().
4. Ops/PM iterates actions and settings without code changes.