Devices

A device is a named surface where the published assistant is deployed. Every public/published link is really the link to a device, so devices are where you manage access and presentation for each place the assistant lives.

Device types: web, mobile, kiosk, other.

Why multiple devices?

So the same brain can appear on your website, in a lobby kiosk, and inside an LMS — each with its own URL, access rules, presentation and analytics — without cloning the assistant.

The default preview device

Every project has one default preview device — the surface that the dashboard Preview button renders through. This lets you preview your assistant exactly as it appears on that device, including any custom HTML template, without visiting a published link.

• The first device you create in a project becomes the default.
• You can switch the default by editing a device and clicking Set as default preview device (only available when the project has more than one device).
• The default device can never be disabled — it’s always on so Preview keeps working, independent of whether the assistant is published.
• The default device can only be deleted if it’s the last device left (at which point Preview has no surface to render through).

Tip: Use the default preview device when building custom templates — set that device’s Custom embed template option to “on”, edit and save the template, then click “Preview template” to test it in that device’s context. This works even before publishing.

Per-device settings

Setting	What it does
Name	Human-readable label (e.g. “Lobby Kiosk”, “Marketing Site”).
Slug	URL-safe identifier used in the public link (…/<deviceSlug>). Unique per project.
Type	web / mobile / kiosk / other — drives grouping and the kiosk map.
Default preview device	(Shown when >1 device exists) Click to make this the device the dashboard Preview button renders through. One per project; the default can never be disabled and can only be deleted if it’s the last device.
Enabled toggle	Turn the device on/off. A disabled device returns a friendly “unavailable” message instead of the chat. (Locked for the default preview device.)
Unavailable message	Custom text shown when the device is disabled.
LTI-only access	Only reachable through an LMS/LTI launch — see LTI-Only Access.
Custom embed template	Serve this device through your custom HTML shell — see Custom Templates.
IP allow-list	Restrict who can open the link by IPv4/IPv6 address. Empty = open to all.
Geo-coordinates + location label	Latitude/longitude and a free-text location, used to place kiosks on the map (see Advanced Topics).

Quick actions

Each device row offers: view analytics, copy URL, edit, delete, and (for custom templates) “preview the draft custom embed template” in a new tab.

Access controls: IP allow-list vs. Allowed Domains

Two different controls are easy to confuse:

• IP allow-list (on the device) controls who can open the link directly. This is how you make a published link genuinely private to specific networks.
• Allowed Domains (on the Embedding tab) controls which external websites may embed the assistant in an iframe. It does not restrict the direct link.

If you need “only these people, from this network,” use the IP allow-list (or LTI-only). If you need “only my website may frame this,” use Allowed Domains.

Choosing an access model

You want…	Use
Internal test only	Preview link (login-gated)
Anyone with the link	Published device link
Only my website may frame it	Allowed Domains
Only these IPs may open it	Device IP allow-list
Only via our LMS	Device LTI-only + LTI setup
Only these named people, personalized & metered	Campaign + recipient links
Signed, tamper-proof embeds	HMAC signing