Assistants
Configure the identity, model, behavior, tools, and checks for an Assistant.
An Assistant is the main configuration unit in Ciele. Each Assistant owns its Knowledge, Flows, draft settings, and publication history.
Setup sections
| Section | Purpose |
|---|---|
| General | Set identity, model, and conversation defaults. |
| Knowledge | Add Sources and FAQs. |
| Flows | Define routing and responses. |
| Tools & Skills | Control runtime tools, API integration, and reusable instructions. |
| Goals | Schedule deterministic answer checks. |
| Guardrails | Check Visitor messages and hide marked answer text. |
| Assistant Help Desks | Select Help Desks for escalation. |
| Style | Set the brand color and launcher position. |
| Authentication | Require Microsoft Entra sign-in for Visitors. |
| Publish | Create and manage the live snapshot. |
Changes affect Preview immediately. The live widget changes only after publication.
Preview can use your connected local Claude or ChatGPT subscription from Settings → AI. The progress panel reports searches and their results. It does not request the model’s private reasoning. A connected model still needs Knowledge Sources to answer organization-specific questions reliably.
Inspect Sources in Preview
Preview shows numbered Source citations inside the Assistant response. Hover over a citation or focus it with the keyboard to see its title and Source details. Press Escape to close the card. Click a citation with a public URL to open the original page in a new tab.
Each sourced sentence or step carries its citation beside the text it supports. A Source can be cited more than once in the same answer. Private documents show a preview without an external link. Sources without an inline reference remain available in the Sources list below the response.
Duplicate an Assistant
Duplication copies configuration and Flows. It does not copy Knowledge content.
Review the new Assistant before publication. In particular, add its required Sources and confirm its Help Desk connections.
Move an Assistant between Organizations
Open the Assistant menu and select Export bundle to download a versioned JSON file. Reading an Assistant permits export.
Select Import bundle as new Assistant to upload the file. Import requires edit access and always creates a new Assistant. Existing Assistants stay unchanged.
The bundle contains the Publication configuration, Flows, Skills, Guardrails, quick replies, and style. It names Collections, Help Desks, and connection providers.
Import matches these names in the destination Organization. Read the import report for missing or ambiguous matches. Flows with unresolved references stay disabled.
Credentials, encrypted values, Conversations, and Visitor data are excluded. Configure credentials after import. API Integrations show Needs setup until credentials are available.
Collection content is not included. Import links existing destination Sources from a matching Collection. Unknown bundle versions are refused before creation.
The API provides GET /api/v1/assistants/{id}/export and POST /api/v1/assistants/import. MCP provides the export and import actions of manage_assistants.