The console
What each console setting does to the copilot: contact channels, files in forms, the Test page, identity verification, roles and erasure.
Most of what the copilot knows and does is set in the console rather than in your build: the persona, knowledge, actions and appearance. This page covers the settings that the other guides only mention, and the Test page where you try them.
Test
A real conversation on your test key, drawn as answer pages the way the SDKs draw them. Pick a test user under Talk as to run signed-in actions (see Use the signed-in user). When the copilot calls a handler that lives in your app, the page asks you for its result.
To watch a real build of your app instead, pair it with the console.
Settings → API keys
The API keys tab holds the keys themselves and the settings that decide what a key may do.
Allowed domains
The websites the web SDK may run on. A browser request from any other origin is refused (a test key also answers on localhost); the mobile SDK is unaffected.
Contact channels
Up to six ways to reach a person: a phone line, an email address or a help page, each with a label and optional hours. The copilot is shown this list and nothing else, and the server checks every contact block against it. An app with no channels is never offered the block. The copilot never chats on a person's behalf or promises one is coming.
Files in forms
Off by default. When it is on, a form may include an upload field for photos or documents, up to 20 MB each. The copilot still never asks for a photo of an ID card, a passport or a bank card, and a form asking for a password or a card number is refused whatever this switch says.
Request verification
Generate identity secret creates the secret your server signs user ids with (see Use the signed-in user). Require a verified identity refuses a turn that names a user without a valid signature. Record confirmations on the server has the device report each Confirm tap before your handler runs, and only a tap the server recorded counts (see Security).
Both switches are off until you turn them on, and only an owner can change them.
Settings → Members & roles
Five roles: owner, admin, developer, analyst and support. An analyst sees aggregate numbers only: no transcripts, no keys, no writes. Any member can be limited to named apps.
Settings → Data retention
How long this app's conversations are kept before a nightly job deletes them. Changing it is an owner's call.
Erase one user deletes one person's conversations (with their messages and rating answers), the notes the copilot kept about them, and their user record. It cannot be undone, and only an owner can do it.