Dashboard overview

Signing in to app.kletso.ai, the layout, environments, search, roles, and what each page is for.

The dashboard at app.kletso.ai is where product and engineering teams configure everything the SDK does not decide: agents, tools, components, triggers, keys and secrets.

Signing in

Enter your work email and you receive a six-digit code (valid 10 minutes, 5 attempts). Your address must be on the workspace allowlist and have a membership. The session cookie lasts 30 days; sign out from the avatar menu.

Layout

  • Left rail: the project switcher at the top (one organisation can hold several projects, for example one per app or customer; owners and admins create new ones from the menu), one entry per page with live counts for agents, open conversations and enabled rules, and at the bottom Docs, Help and the backend toggle (Live runtime · api or Demo data · in-browser, which runs the whole dashboard on sample data in your browser).
  • Top bar: breadcrumb, the environment pill (click to switch Development / Production; numbers, keys, conversations, events and rule scope follow it), Search (⌘K), avatar menu.
  • Toasts confirm every mutation bottom-right; failures show the error message.
  • Destructive actions (archive, delete, revoke) ask you to type the resource name.

Roles

RoleCan
viewerRead everything
developerPlus edit agents, tools, workflows, triggers, components, knowledge, and add or rotate secrets (values are never readable)
adminPlus API keys, webhooks, settings, invite and remove members, rename project
ownerPlus change roles

The UI shows every control to everyone; the API enforces the role. A membership can also be limited to specific projects (for example a customer who should only see their own project); such members see only those projects in the switcher.

Pages

PagePurposeDocs
OverviewSetup checklist, 7-day numbers, recent conversations and errors for the selected environment
AgentsAgents list and the builder with live previewAgents
WorkflowsVisual builder, test run, publishWorkflows
ToolsHTTP tools, auth, confirmation, testTools
ComponentsBuilt-in and custom types, sync from code, fixturesComponents
Triggers & notificationsRules, simulator, push credentials and devicesTriggers
KnowledgeSources and retrieval test (indexing planned)Roadmap
Conversations, Events, Users, AnalyticsInspect what happenedConversations and events
WebhooksEndpoints and signing secrets (delivery planned)Roadmap
API keys, SecretsCredentialsKeys and secrets
SettingsMembers, project, end-user auth, widget branding, audit logSettings

Setup checklist

The Overview page tracks six steps: create an agent, add a tool, publish a version, copy an API key, install the Flutter SDK (done when the first conversation arrives), sync components from code. When all six are done the card is replaced with a summary.

Last updated 2026-09-28 · Report an issue with this page