- Go into Channels and find (or create) your Copilot Assistant-type channel (manual 24, section 12) — it’s its own channel type, with its own plan limit (manual 62).
- Tap “Open copilot settings”, inside that instance’s “Copilot” section.
- Turn on the “Turn on the copilot for this channel” toggle.
Below it, the “Initialization code” appears: it’s the second block your developer pastes right after the widget snippet on their site (manual 06) to start the copilot on that page. Without that step, the widget keeps working like a normal chat.
2.1 The manifest: pending, approved, outdated
Section titled “2.1 The manifest: pending, approved, outdated”The manifest is the closed list of screens and actions your developer prepares on their site for the copilot to be able to use. It’s sent by the very browser of whoever visits that site, so before turning it on, you review and approve it: only an approved manifest arms the copilot, and any later change on the site leaves it “outdated” until you approve it again.
- Review the diff (which screens and actions changed) and tap “Approve”.
- Confirm in the “Approve this manifest version?” dialog — the notice reminds you the actions stay off until you turn them on one by one (section 3).
Important — Revoke turns off the copilot instantly
The “Revoke” button turns off the copilot in every open session on that site immediately. Use it if you suspect the manifest isn’t trustworthy, or if you want to turn off the copilot on that site without touching the rest of the channel’s settings. You can approve another version later.
Note — Not sure whether to approve? Think about who wrote the manifest
A manifest is a JSON document you control if the channel is your own site (or the one the Platform already ships for its own “Assistant” panel, already reviewed by your provider). Before approving a new version, confirm with your own development team that the change is the one you expected.