# Dashboard Guide

This guide explains the OpenClaw control panel in plain English.

The dashboard is where you can see whether your assistant is running, connected, and healthy.

You do not need to understand every technical detail to use the assistant.

For beginners, the safest rule is:

Use the Chat page for normal work. Use the Control pages mostly for checking status, not changing settings.

---

## 1. What The Dashboard Is For

The dashboard helps you:

- open the assistant chat
- check whether the assistant is running
- see connection status
- view sessions
- inspect usage
- see available agents
- see available skills
- see connected nodes or devices if configured
- manage advanced features later

The dashboard is not where most users should "work."

Most normal work happens in Chat.

---

## 2. Safe Beginner Areas

These areas are usually safe to look at:

- Chat
- Overview
- Sessions
- Usage
- Agents
- Skills
- Docs

Looking is safer than changing.

If you are not sure what a button does, ask the assistant before clicking it.

---

## 3. Areas That Need More Care

These areas can be more advanced:

- Channels
- Instances
- Cron Jobs
- Nodes
- Gateway Access settings
- Tokens
- WebSocket URLs
- Session keys

These can affect connections, scheduled jobs, devices, or how the assistant talks to other services.

Do not change these unless you know why you are changing them.

---

## Quick Answer: Gateway Access And Safe Clicks

Gateway Access is how the dashboard connects to the assistant engine.

- WebSocket URL is the connection address.
- Gateway Token is a private access key. Do not share it publicly.
- Default Session Key tells the dashboard which assistant/session to open.
- Usually safe to view: Chat, Overview, Docs, Usage, Sessions, Agents, and Skills.
- Use caution with: Gateway tokens, connection settings, Channels, Instances, Cron Jobs, Nodes, stop/restart/delete/edit buttons, and anything that connects accounts or changes services.

Best beginner rule:
Look first. Ask before changing.
## 4. Chat

What it is:
The normal place to talk with your assistant.

Use this for:

- asking questions
- writing drafts
- summarizing documents
- getting help with files
- asking what to do next
- asking for explanations
- testing what the assistant can do

Beginner tip:
Start here.

Good first question:
"What can you help me do?"

---

## 5. Overview

What it is:
The status page for the assistant system.

It usually shows whether the gateway is connected and healthy.

You may see items like:

- Status
- Uptime
- Tick Interval
- Last Channels Refresh
- Gateway Access
- WebSocket URL
- Gateway Token
- Default Session Key
- Language

Plain-English meaning:

- Status tells you whether the system looks healthy.
- Uptime tells you how long it has been running.
- Tick Interval is part of the system's background timing.
- Last Channels Refresh tells you when connection channels were last checked.
- Gateway Access is how the dashboard connects to the assistant engine.
- WebSocket URL is the connection address.
- Gateway Token is a private connection key.
- Default Session Key tells the system which assistant/session to open by default.

Safety note:
Do not share gateway tokens publicly.
Do not post screenshots that reveal private tokens.
Do not change connection settings unless you know why.

---

## 6. Gateway Access

What it is:
The connection area that lets the dashboard talk to the assistant engine.

You may see:

- WebSocket URL
- Gateway Token
- Password
- Default Session Key
- Connect button
- Refresh button

Plain-English meaning:

The dashboard is like a control screen.
The gateway is the doorway to the assistant engine.
The token or password helps prove that the dashboard is allowed to connect.

Beginner rule:
If chat is working, do not change gateway settings.

Safety note:
Treat gateway tokens like private access keys.

---

## 7. Channels

What it is:
Channels are ways the assistant can connect to communication services.

Examples may include:

- WhatsApp
- Telegram
- Discord
- Signal
- iMessage
- other messaging services

Current beginner advice:
Do not connect personal messaging accounts casually.

Channels may require setup, credentials, and permission.

Safety note:
A connected channel may allow the assistant to read or send messages. That should only be enabled through a supported setup process.

---

## 8. Instances

What it is:
Instances are running copies or processes of the assistant system.

Plain-English meaning:
An instance is like a running engine.

You may use this page to check whether something is running.

Beginner rule:
Do not stop, restart, or change instances unless you are troubleshooting with guidance.

---

## 9. Sessions

What it is:
Sessions are conversations or conversation workspaces.

Use this to understand or manage:

- active chats
- prior sessions
- session keys
- where a conversation belongs

Plain-English meaning:
A session is like a named conversation or workspace.

Beginner tip:
If you are confused, start a new chat session rather than changing technical session settings.

---

## 10. Usage

What it is:
Usage shows activity, cost, or resource information depending on the setup.

It may help answer:

- how much the assistant has been used
- which model or tools were used
- whether usage is increasing
- whether there may be cost concerns

Beginner rule:
Usage is usually safe to view.

Safety note:
If API billing is connected, usage can affect cost. Ask before enabling high-volume automation or repeated searches.

---

## 11. Cron Jobs

What it is:
Cron jobs are scheduled tasks.

They can tell the assistant or system to do something repeatedly.

Examples:

- check something every hour
- run a daily cleanup
- refresh data
- perform a scheduled report

Beginner rule:
Do not create scheduled tasks casually.

Safety note:
A recurring task can keep running even after you forget about it. This can affect cost, privacy, files, messages, or connected accounts.

Good safe question:
"What will this scheduled task do, and how can I stop it?"

---

## 12. Agents

What it is:
Agents are assistant profiles or roles.

An agent may have:

- a name
- instructions
- tools
- memory
- a purpose

Plain-English meaning:
An agent is a version of the assistant with a job.

Examples:

- general assistant
- project helper
- research assistant
- coding helper
- personal organizer

Beginner rule:
Use the default agent first. Do not create many agents until you understand what each one is for.

---

## 13. Skills

What it is:
Skills are optional abilities the assistant may use.

Examples might include:

- reading PDFs
- summarizing text
- web searching
- working with files
- using connected services
- special integrations

Plain-English meaning:
Skills are like add-on abilities.

Beginner rule:
Do not assume every listed skill is fully configured. Some skills need accounts, API keys, or setup.

For a plain-English list of abilities, ask:
"Show me the tools catalog."

---

## 14. Nodes

What it is:
Nodes are other connected devices, computers, or workers.

Plain-English meaning:
A node is another machine the assistant may be able to communicate with.

Beginner rule:
Do not connect other devices casually.

Safety note:
Connected nodes can increase what the assistant can access. Only use nodes through a supported setup process.

---

## 15. Docs

What it is:
Docs are the built-in documentation.

Some docs may be technical.

Beginner tip:
If a doc is confusing, ask:
"Explain this page in beginner language."

---

## 16. Search Box

What it is:
The dashboard may include a search box.

Use it to find:

- settings
- docs
- sessions
- agents
- control panel sections

Beginner tip:
Search is useful when you do not know where something is.

---

## 17. What Is Safe To Click?

Usually safe:

- Chat
- Overview
- Docs
- Usage
- Sessions for viewing
- Agents for viewing
- Skills for viewing

Use caution:

- Connect buttons
- Refresh buttons that affect services
- edit buttons
- delete buttons
- restart buttons
- stop buttons
- token/password fields
- channel setup buttons
- cron job controls
- node controls

Best rule:
If a button sounds like it changes something, ask first.

---

## 18. What Not To Share

Do not share screenshots that reveal:

- gateway tokens
- passwords
- API keys
- private session links
- private account information
- private messages
- personal documents
- billing details

If you need help, crop or blur sensitive information before sharing screenshots.

---

## 19. Best Beginner Workflow

Use this workflow:

1. Open Chat.
2. Ask what the assistant can do.
3. Use Overview only to confirm the system is healthy.
4. Use Docs if you want to learn more.
5. Use Sessions if you need to find a prior conversation.
6. Use Usage if you want to check activity or cost.
7. Ask before changing Channels, Cron Jobs, Nodes, Gateway Access, or Instances.

---

## 20. Good Questions To Ask The Assistant

- "What does this dashboard page mean?"
- "Is this safe to click?"
- "What is a gateway token?"
- "What is a session?"
- "What is a skill?"
- "What is a node?"
- "What is a cron job?"
- "What should I avoid changing?"
- "Can you explain this screenshot?"
- "What should I do next?"

---

## 21. Simple Summary

The dashboard is the control panel.

Chat is where you work.

Overview shows health.

Sessions show conversations.

Usage shows activity.

Agents are assistant roles.

Skills are abilities.

Channels connect communication services.

Cron Jobs run scheduled tasks.

Nodes connect other devices.

Gateway Access controls how the dashboard connects to the assistant engine.

For beginners:
Look first. Ask before changing.
