Skip to content

Deployment Overview

Before diving into URLs, embed codes and access rules, it helps to hold three ideas in your head:

  • A project is one assistant — its persona, knowledge base, flows and settings.
  • Publishing takes a frozen snapshot of that assistant and makes it reachable to the outside world. Editing the assistant afterwards does not change what the public sees until you publish again.
  • Channels are the individual surfaces the published assistant is served on (a website embed, a lobby kiosk, an LMS activity, …). Every public link points at a channel, and analytics, access rules and custom templates are configured per channel.

The journey is always:

Build assistant → Preview (internal test) → Publish (snapshot)
→ Deploy on one or more Channels → Share / embed the channel link

Everything in this guide lives under Dashboard → Deployment unless noted otherwise.

The Deployment page has six tabs: Channels, Campaigns, Embedding, Custom template, Discoverability and Map.

Purpose URL shape Audience
Preview (internal test) /chat/<projectId> Org members only
Published, per channel /chat/<orgSlug>/<projectSlug>/<deviceSlug> Public (+ channel rules)
Custom template (live) /embed/<orgSlug>/<projectSlug>/<deviceSlug> Public (+ channel rules)
Custom template (preview) /embed/<projectId> Org members only
Personalized recipient (campaign) /i/<token> The one recipient, while campaign is active
  • Preview & Publishing — the difference between your internal test link and the public link, and how the snapshot model works.
  • Devices — named deployment surfaces with per-channel access rules, analytics and settings.
  • Custom Templates — wrapping the chat in your own branded HTML page.
  • Embedding on a Website — iframe snippets, external variables, HMAC signing, download packages.
  • LTI-Only Access — restricting a channel to LMS launches.
  • Campaigns & Recipients — time-boxed, metered outreach with personalized links.
  • Advanced Topics — user types & library visibility, kiosks & GPS, access-model decision table, data out.