Configure Assistants

An assistant is the primary boundary for configuration, knowledge, Captured Questions, Insights, embed credentials, and scoped access.

Access and plan limits

Creating, reading, updating, and deleting use assistants.create, assistants.read, assistants.update, and assistants.delete. Assistant scope applies after creation. Workspace limits are generated in Plans and Billing.

Create and configure

1. Open Assistants and create an assistant.
2. Set a clear internal/public name and behaviour.
3. Add current sources in Knowledge.
4. Configure widget appearance, greeting, support URL, placement, allowed domains, and logging in the dashboard.
5. Where exposed by advanced settings, review retrieval/model parameters carefully; test rather than assuming a “deeper” setting is better.
6. Preview two common questions, one edge case, and one question the source cannot answer.
7. Install it using Embed and Deployment.

Status and destructive actions

A disabled assistant cannot be used normally until re-enabled. Plan enforcement can also disable assistants above a downgraded quota. Deleting an assistant is irreversible and can affect its external assistant/vector-store resources. Confirm the assistant name and preserve required evidence or source records before deletion.

Verify a change

After any material update, verify preview output, an allowed-domain deployment, and the appropriate Captured Questions/Insights scope. Configuration changes may not appear immediately in a browser with cached authenticated settings; use a private window when validating.

See Configuration, Roles and Permissions, and Troubleshooting.