/startWelcome and usage help/Overview
Open Telegram ↗WORKSPACE OUTCOMES
What the team is moving
Track delegated outcomes, review decisions, and open completed work.
PRIMARY INTERFACE
Checking Telegram…
Reading bot and webhook status.
ACTIVE WORK
Outcomes in progress
DECISIONS
What needs your attention
RECENT OUTCOMES
Completed work
SERVICE READINESS
Connected services
PRIMARY USER CHANNEL
Telegram
Connection, webhook delivery, and the commands available to users.
CONNECTION
WEBHOOK
Inbound endpoint
Telegram sends messages to this server endpoint. The secret remains in Vercel.
Loading…USER ACCESS
Telegram accounts
Every person needs a single-use invitation created for their exact Telegram username.
SUPPORTED COMMANDS
/todayActive work and decisions/teamConfigured AI workers/decisionsReview the next pending approvalPlain messageAsk the company to do or remember somethingCONFIGURATION
AI workers
Assign reusable skill and access roles to each worker.
ROLE LIBRARY
Role templates
Like cloud roles: each template bundles skills, access, and approval boundaries.
COMPANY CONTEXT
Knowledge
Durable facts workers may use when responding in Telegram.
GOVERNANCE
Rules & approvals
Review how independently workers may act and which decisions return to an administrator.
PENDING
Approval queue
AUDIT & DIAGNOSTICS
Operations
Real delegated work, failures, and recorded system events.
WORK
Tasks
AUDIT LOG
Activity
ADMINISTRATION
Settings
Workspace identity, deployment services, and first-run configuration.
Every outbound email pauses for an administrator to approve the exact recipient, subject, and body. Requesting changes sends nothing.
The control panel uses one administrator token. Telegram users require personal, single-use invitations managed on the Telegram page.