Skip to main content

Dashboard Guide Overview

This section is the guide for the Clark web dashboard. It helps workspace owners and admins understand what they can see, check, and configure in the browser. It is not the full chat user guide: day-to-day work still happens mostly inside Telegram or Slack.

Web dashboard

Review chats, documents, tasks, CRM, memory, billing, and team settings from one place.

Chats stay primary

Use Telegram or Slack for questions, summaries, tasks, reminders, and everyday collaboration.

Admin actions

Use the dashboard when you need setup, cleanup, visibility, permissions, or billing changes.

The Clark dashboard is the control room for your workspace. It shows connected chats, processed documents, tasks, templates, CRM records, team members, usage, and account settings.

Main Workflow

  1. Connect a Telegram or Slack workspace.
  2. Let Clark observe team conversations and documents.
  3. Mention Clark when you want an answer, summary, task, CRM action, document action, or follow-up.
  4. Use the dashboard to review structured results and manage settings.

Dashboard Sections

SectionUse it for
OverviewWorkspace health, recent documents, tasks, and usage snapshots.
TasksList, kanban, and calendar views for team work.
DocumentsProcessed files, extracted details, summaries, and filters.
TemplatesReusable DOCX templates and generated documents.
CRMLeads, deals, contacts, notes, and pipeline status.
TeamMembers, roles, permissions, and invite status.
ChatsConnected Telegram and Slack chats, master chat, listener mode, and recent context.
MemoryPeople, companies, facts, and extracted entities Clark can reuse later.
StoreAdd-ons such as token packs or custom services.
BillingPlan, usage, limits, invoices, and subscription controls.
SettingsBot identity, chat behavior, summaries, and CRM/ERP integrations.

Safe Usage Principles

  • Keep sensitive data inside approved workspace chats.
  • Mention Clark only when you need a response.
  • Use the master chat for owner-level cross-chat questions.
  • Review generated documents before sending them outside your company.
  • Keep team roles current so only the right people can access admin actions.