Skip to content
Dot
DocsSign inGet started

Core concepts

Workspaces, roles, channels and the boundaries the platform enforces.

Accounts, organizations, workspaces

A user belongs to one or more organizations. An organization owns workspaces. Everything you build lives in a workspace, and a workspace is the tenant boundary: every record carries its workspace, every query filters on it, and PostgreSQL row-level security enforces it a second time underneath.

Roles

RoleCan do
OwnerEverything, including deleting the workspace and managing billing when it exists.
AdminManage members, integrations, credentials, API keys, and delete resources.
MemberCreate and edit chatbots, agents, workflows, knowledge and CRM records.
ViewerRead dashboards, conversations and records. No writes, and no playground runs.

Roles are checked on the server for every request. A control hidden in the interface is a convenience, never the boundary.

Chatbots and agents

A chatbot answers questions from its instructions and its attached knowledge. An agent adds tools, a memory window, structured output and an approval step. Start with a chatbot; move to an agent when the assistant needs to *do* something rather than only answer.

Channels

Every conversation records where it came from, so reporting can separate real traffic from your own testing.

ChannelSource
widgetThe embedded website widget.
apiA server-to-server call authenticated with a workspace API key.
playgroundTesting inside the dashboard.
agentAn agent run.

Usage and metering

Messages and token counts are recorded per workspace as they happen, and surfaced in Analytics. There is no quota enforcement or billing yet; see rate limits for the ceilings that do apply.