AiHummer
English▾
Log in
v1.0.x▾
v1.0.xstable
{ }Swagger
Web UI/Web UI overview

Web UI overview

v1.0.x · updated 2026-07-08

The Web UI is the AiHummer gateway admin console: the single place where you build and configure AI employees, connect channels and models, fill the knowledge base, manage access, budgets and security, read sessions, and watch system health. It is a separate interface from the Customer portal (my.aihummer.ru), which handles billing and the lifecycle of a managed cloud instance.

This documentation group describes every Web UI screen: what it is for, how to use it, and how to configure it.

Opening the Web UI

The Web UI listens on a separate private port (default :8781), not on the public message-ingest port. Its address and availability are configured on the External access & API page (AIHUMMER_WEBUI_ENABLED, AIHUMMER_WEBUI_ADDR). The first sign-in and the initial admin password are covered in First login.

The sidebar is organized into five collapsible groups:

  • Work — Dashboard, Agents, Orchestration (graphs), Sessions.
  • Memory — Einstein memory, Facts, Knowledge base, Skills, Shared blocks, Prompts, Instructions.
  • Channels — Channels, Plugins, Connections, Webhooks.
  • Control — Notifications, Approvals, Changes, Moderation, Budget, Audit, Analytics, Logs, Status, Support.
  • Manage — Workspaces, Users, Roles, Members, Secrets, Settings, Models, API keys, External access, IP allowlist, Schedules, License, System, Account.

The active page is stored in the URL hash (#<section>), so any screen is directly linkable. Pages load themselves on open — there are no “Load” buttons; screens with live data (Sessions, Logs, Dashboard, plugin installs) poll the server periodically.

Role-based visibility

Some tabs are flagged admin-only and hidden from roles below admin/owner. What a user sees depends on their role and the permissions from RBAC. An operator sees the working screens (sessions, approvals) but not secrets, license or system management.

Workspaces

Many screens (Agents, Orchestration, Skills, Schedules, BYOK) are scoped to a workspace and carry a workspace selector at the top; the active workspace is selected by default. Workspaces are created and switched on the “Workspaces” screen. See multi-tenancy for the model.

Common patterns

  • Search the docs from the toolbar button or ⌘K / Ctrl+K.
  • Creating entities always happens in a modal; editing is inline.
  • Every page has a link to the matching section of this documentation.
  • Fields have “?” hints — hover to learn what a parameter does.

Next