> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ada.cx/docs/channels/messaging/messaging-configuration/launch-options/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ada.cx/_mcp/server.

# Launch options

## Overview

Control where [Messaging](/docs/channels/messaging) is available and which visitors see the hosted widget.

## Limitations

[Messaging](/docs/channels/messaging) launch settings do not upgrade bundled legacy SDKs. Complete the applicable [installation](/docs/channels/messaging/messaging-configuration/installation) first.

An empty **Allowed websites** list permits the standard widget on any website. Custom apps require an approved origin even when that list is empty.

## Capabilities & configuration

Configure [Messaging](/docs/channels/messaging) under **Config > Channels > Messaging > Launch**.

* **Messaging availability** controls whether the channel is enabled.
* **Allowed websites** restricts where the widget can be embedded and which custom app origins are accepted.
* **Launch controls** splits visitors into three groups: no widget, your primary AI Agent, and an alternative AI Agent.
* Each visitor keeps the same AI Agent on later visits.
* The alternative AI Agent's **Allowed websites** list must include your page.
* The preview link opens the page with the alternative AI Agent.

Availability and allowed website settings require the appropriate dashboard permissions.

## Implementation & usage

Verify [Messaging](/docs/channels/messaging) on each approved host before you increase its rollout percentage.

**To configure launch settings:**

1. Open **Config > Channels > Messaging > Launch**.
2. Set **Enable Messaging** for the channel's intended availability.
   Changes to **Enable Messaging** save automatically.
3. Add the approved hostnames or origins under **Allowed websites**.
4. Set the rollout percentage under **Launch controls**.
5. Click **Save** after editing **Launch controls**.
6. Test the result from each target website.

For a custom app, approve its HTTPS origin before deployment. Use an origin your organization controls.

Share the [custom app configuration requirements](/messaging/custom-apps/getting-started) and [security guide](/messaging/web/security-best-practices) with your developers.

Dashboard testing can bypass normal rollout controls. Confirm production visibility with a normal website session before launch.

## Related features

Review [Installation](/docs/channels/messaging/messaging-configuration/installation) and [Data controls](/docs/channels/messaging/messaging-configuration/data-controls) with your launch settings.

---

Have any questions? Contact your Ada team, or email us at [](mailto:help@ada.cx?subject=Help%20Docs%20inquiry).