Configuration

Hosted app configuration is the published settings the embed loads with a publishable key. Chat is embed-only. There are no public chat URLs. Message bodies are never part of configuration and must not be sent through MCP.

Local / BYO vs hosted config

  • Local / BYO adapter: you can pass optional config props or rely on widget defaults.
  • Hosted config: create an app, edit a draft, publish a revision, then pass appId + publishable key. BYO plans still use hosted config for toggles while messages stay on your backend.

What the client loads

Published config includes app id, name, revision, and:

  • allowDirect
  • allowGroups
  • allowAttachments
  • allowMemberManage
  • requireAuthorToken (default false)
  • emptyState
  • allowedOrigins (default * for first run; set exact origins for live)
  • branding (optional title, primaryColor, logoUrl)

Body max 4,000 and groups max 20 are package limits, not free-form config strings. See limits.

Draft, publish, fetch

Edit drafts in the dashboard or via secret-key / MCP APIs, then publish. Live clients keep the last published revision until you publish again. See Configuration revisions.

Live bsw_live_pub_ config fetch needs BYO ($9.99) or Hosted ($19.99). Publishing alone does not grant live entitlements.

Branding

Optional branding.title can override the heading the widget shows. primaryColor sets the accent. Optional logoUrl renders beside the title when present in published config.

Related: Revisions · Apps · Origins · React component · API overview