Skip to main content

Operator Guide

This section is for the person Blockway hands the dashboard URL to when a Claway deployment goes live. It answers the questions that come up in the first two weeks of operating a Jarvis for a team:

  1. Getting started — first login, TOTP setup, what each dashboard page is for.
  2. Persona guide — how to write a persona that holds up in production, how the AI Assist helper works, why the "KB-first rule" matters.
  3. Knowledge base guide — how to upload documents, how per-chat scoping works, the security model that keeps groups isolated.
  4. WhatsApp group onboarding — the five-step wizard for bringing a new group online without editing config.yaml by hand.
  5. When to escalate — signals that mean call Blockway support instead of continuing to poke at it.

Who this section is not for​

  • If you're a Blockway engineer, you want the developer guide instead.
  • If you're the person chatting with Jarvis inside a WhatsApp group, ask your operator for the "End-user cheat sheet" — it's a one-page handout, not a docs section.

The mental model in one paragraph​

One Claway deployment. One WhatsApp / Telegram / Signal bot account. Many groups, each running its own persona (an accounting clerk, a sales assistant, whatever the customer needs), each with its own memory, each with its own skills enabled, and each with its own knowledge base scope. Groups are isolated at the SQL level — a document in the "accounting" KB is never returned to the "customer service" group's agent. The operator dashboard is the single control surface.