Welcome
Welcome to the Cere Insight 2.0 documentation. It is written for people learning the product from scratch, running day-to-day operations, integrating via API, and using advanced AI features.
What to take from this page
- In 5 minutes: Understand the problem space (what the product does — and does not).
- In 30 minutes: Read Concepts and architecture and Quick start to draft your first project.
- In a day: Navigate boards, knowledge bases, test mode, and reports confidently.
Screenshot
The main shell after sign-in (sidebar + navbar + dashboard) is a good hero image here.
What is Cere Insight?
Cere Insight 2.0 is a platform for enterprise teams to manage AI chatbots, knowledge sources, and operational reporting in one web UI. It organizes around three ideas:
- Design — Projects, agents, tools, and the visual board express how the bot behaves, both technically and visually.
- Feed — Knowledge bases and external API integrations connect real-world data the bot can use.
- Measure — Reports and analytics agents monitor conversation operations and business data.
It is not a “magic box”: system prompts, router design, fresh knowledge bases, and live agent workflows all matter.
Main building blocks (one-liners)
- Projects (Bot Apps): One end-to-end chat experience: name, description, default LLM settings, and board layout.
- Board: Model flow with nodes and edges: routers and sub-agents, tools, integrations, knowledge bases, inbox links.
- Knowledge bases: Upload documents and make them searchable via embeddings; agents can answer with RAG.
- Live messaging: Channels (widget, email, WhatsApp) bound to projects through inboxes, alongside live agents where needed.
- Analytics agents: Separate module for dashboards and natural-language queries over business data.
- Orchestration: Event-driven workflows (requires the feature in subscription).
- Reports: Operational summaries from live messaging and live agent data; contact reports at
/reports/users.
See Concepts and architecture for relationships.
Who uses which screens?
| Persona | Typical day | Docs |
|---|---|---|
| Product / ops | Project cards, board tuning, KB updates, report pages | Project management, Knowledge bases, Reports |
| Developer | API integrations, tools, webhooks | API integrations, Projects API |
Org admin (ORG_ADMIN) | Invites, roles, watching limits | Organization, Roles |
Super admin (SUPERADMIN) | Multi-tenant platform settings, messaging environment registry | Messaging environment instances |
Do not mix role types
Account role (USER / SUPERADMIN) is not the same as membership role (ORG_ADMIN / MEMBER). See Authentication.
Typical first-week story
- Invited to an org → Authentication.
- See quota cards on the dashboard → Dashboard.
- Open a first project, add a router and two specialists → Agents.
- Upload PDFs to a KB and wait for embeddings → Knowledge bases.
- Wire tools on the board, validate in test mode → Project management.
- Ops connects an inbox and ships the widget → Live chat.
FAQ (first week)
Why can’t super admin create a project?
Project routes expect an organization context; the backend blocks super admins without org for that flow. Create projects as an org member. See Concepts and architecture (super admin tip under system architecture).
401 and I’m sent to login — where is the token?
Middleware checks the access_token cookie; the API client sends Bearer + X-Organization-Id. Session may have expired or the org header may be missing. See Authentication.
Board not saving / test mode stuck
Ensure the project saved; then check Redis/queues and server logs (your deployment). User-facing flow: Test mode.