Learning path

This page is the recommended order to learn Cere Insight 2.0 from zero to production-style usage. Each step targets an outcome: understand a concept, recognize a screen, or finish an integration.

Stage 0 — Mental model (~20 min)

Goal: Internalize vocabulary and where pieces live.

1. Concepts and architecture — glossary, diagram, FE/BE maps.
2. Welcome — personas and first-week story.

Check: Can you explain why X-Organization-Id is required, in your own words?

Stage 1 — Account and shell (~30 min)

Goal: Session, roles, and not getting lost in the UI.

3. Authentication — JWT, cookies, multi-org, Google OAuth.
4. UI guide — sidebar groups, reports submenu, responsive behavior.
5. Profile and settings — language and preferences (deployment-dependent).

Check: Contrast ORG_ADMIN vs SUPERADMIN with a concrete action (e.g. inviting a member).

Stage 2 — Organizational context (~45 min)

Goal: Team and quota awareness.

6. For admins: Organization, Roles and permissions.
7. Subscription — limits, plan features, model allowlists (may align with backend SubscriptionFeatures).

Check: Which actions return 402 or a limit error?

Stage 3 — First bot skeleton (1–2 hours)

Goal: A working test loop (board + test mode).

8. Quick start — checklist.
9. Dashboard — org snapshot.
10. Project management — list, board panels, test mode, AI Builder panel.
11. Feature depth: Projects, Agents, Tools.

Check: How would you model multiple specialists on the board without a router agent?

Stage 4 — Knowledge and external systems

Goal: RAG + APIs.

12. Knowledge bases + RAG.
13. API integrations + External API.

Check: First three checks when embedding status is FAILED.

Stage 5 — Live channels and operations

Goal: From test traffic to real conversations.

14. Live chat and messaging — channel types, widget, inbox.
15. Reports — overview through bot; Contact reports (/reports/users).

Stage 6 — Analytics, orchestration, advanced AI

Goal: Value beyond chat: data and automation.

16. Analytics agents — sources, dashboards, NL queries.
17. Orchestration — workflows and triggers; workflows feature flag.
18. AI Builder, AI Autofill, Analytics bot.

Stage 7 — API and automation

Goal: Connect external systems.

19. API authentication — Bearer, org header, errors.
20. Common endpoints: Projects, Knowledge bases, Live chat (path prefixes depend on environment).

Super admin track

• Messaging environment instances
• Subscription plans (if your deployment uses central plan management)

Next step

Jump to Quick start for Stage 3, or pick the stage where you feel weakest above.