Workspace Structure
The main areas inside Raydo Desktop and what each one is for.
When you first open Raydo, you do not need to understand every screen. The main path is simple: start work first, then bring in roles, skills, workflows, and controls as you need them.
The areas you will use most often
Dashboard
The place to check the big picture. Useful for seeing what is active, what needs attention, and whether the system looks healthy.
Inbox
The place for follow-up work. Useful for bringing back items that still need action instead of leaving everything buried inside chat history.
Chat
The place to start a task. You can begin directly, or start with role, skill, or workflow context when you want stronger structure.
The areas for structure and assets
Projects / Organizations / Roles
These pages help define the work context and responsibility structure. They become more useful once your usage starts to settle into patterns.
Templates / Skills / Workflows
These pages help you keep methods. They are where repeatable roles, reusable capabilities, and fixed paths start to take shape.
The areas for execution and control
Runs / Approvals
These pages help you review execution and key confirmation points. They matter more once work volume grows or collaboration becomes more involved.
Channels / AI / MCP
These pages connect models, tools, outside entry points, and runtime methods. They support the workspace, but most users do not need to master them on day one.
Settings
The place for account info, preferences, system details, and basic configuration.
A practical order to learn it
- Start in Chat and get a first result
- Check Dashboard and Inbox to see how work continues
- Add Roles, Skills, and Workflows when patterns start repeating
- Move into Runs, Approvals, Channels, AI, and MCP when you need more control
If you see focused and full
These are not two different products. They are two levels of information density inside the same workspace. New users do not need to open everything at once.