Product introduction

Who this is for: People who want AI to speed up day-to-day and team work, team leads, and anyone who needs to put an assistant into a system they already run.

How to use this page: Get a quick picture of what Cadau can do for you. For on-screen steps, ask the help assistant in the product, or see the feature notes under help/ and the Product handbook.

---

What Cadau is

Cadau is an AI assistant for companies and teams. You can think of it as:

• A work-assistant platform that learns, remembers, and can be tailored;
• A workspace for each team, so chat, knowledge, agents, lightweight apps, and controlled data stay inside the right bounds;
• Conversation you can embed in the systems you already use (or add as a platform plugin), so the assistant shows up on the page where work actually happens.

Unlike a one-off chat you throw away, assistants in Cadau can accumulate memory and skills across conversations, cite the knowledge base you maintain, and — within authorization — query business data, produce charts, change an app’s interface, and generate office documents. The more you use it, the closer it gets to your team’s voice and habits.

---

Who it is for

---

Why Cadau

The assistant grows — it is not only chat

Work assistants in Cadau can:

• Remember preferences, decisions, and project progress you have confirmed (still valid across conversations);
• Cite knowledge the team and individuals maintain, so answers have a basis;
• Accumulate skills, turning repeated ways of working into reusable capability;
• Extract useful information from conversation within authorization, so you do not have to re-explain;
• Improve skills and app UI through conversation (preview a revision, then confirm), so changing configuration becomes natural-language collaboration.

Team bounds are clear

• Each workspace is a collaboration boundary (company, department, project, and so on);
• Team knowledge, apps, skills, and enabled assistant capabilities in a workspace are shared among members according to authorization;
• Personal memory and private materials are not shared with colleagues by default; workspaces do not cross each other’s bounds.

Conversation as action: say you want it done, and it does it

You do not have to learn where the menus are first. Tell the help assistant “create a workspace for me”, “switch to…”, “create an agent”, “invite a colleague”, “generate a skill”, or “create an app” — it will ask for anything missing and then do it. When you open Human Resources, Warehouse, Compliance, Email, or Cameras, tell the app assistant “list departments”, “receive stock”, or “who clocked in today” and it acts the same way. Only when you ask “how / how do I” does it answer with a guide and a page entry. Creating, renaming, switching, or deleting a workspace does not require a workspace to be selected first; when one is selected, creating an agent writes into the current workspace.

One entry, several ways to use it

• Web and mobile feel the same; you can talk after you sign in;
• With no workspace selected, the help assistant both answers “how do I use this” and can create or rename a workspace for you; after you pick a workspace, you can also create agents, draft skills, create apps, and manage data connections in conversation; on other modules, the action assistant in the lower right jumps back to the same help conversation, with contextual suggested questions;
• After you pick a workspace, use My agents for real work;
• Third-party pages can connect through an embedded assistant, or you can put a specialist system on the workbench as a platform plugin.

Safe and governable

• Model calls and secrets are hosted on the server, not exposed to the browser;
• Knowledge layers, memory ownership, member permissions, data connections, and network scope can all be governed by company and workspace policy;
• Queries mainly use predefined queries and authorized resources; changes can require approval; assistant behavior is configurable and auditable.

---

Capabilities at a glance

Messages: talk with an assistant

• After you register, you land in Messages and start with the help assistant to learn the product;
• After you pick a workspace, choose a work assistant on the left and start a multi-turn conversation;
• Supports multiple conversations, attachment upload, and stop generating; you can tap “Remember” on important content;
• A work-assistant conversation has a topic (what this conversation is meant to get done — you can change it); say you want a bit more, a different version, or a summary, and the assistant does it — you do not have to memorize commands;
• Tables, documents, and images the assistant produces can be viewed on the right; you keep talking in the bubble. When there is a result, the features menu and conversation list step aside; you can also pin the conversation list;
• Service notifications always appear in the Messages list (for example, workspace invite progress): read-only, tappable actions, not a regular conversation;
• You can also make a presentation (generate .pptx), read and write office documents within authorization, produce charts, and — on a model that supports image generation — say generate a picture of…, among other extensions.

Difference from Contacts: Messages is for AI assistants and system notifications; Contacts is for real colleagues and friends (direct chat and workspace groups).

Workspace collaboration: a team space

• Create / switch / invite workspaces so different teams stay separate;
• Maintain a workspace knowledge base — team policy, project notes, internal wiki — shared by every agent in that workspace;
• Members join through invite or request to join; admins can turn on assistant capability packs and configure support queues here.

Assistant capability packs: turn on what the assistant can do

Workspace admins turn these on in Workspace collaboration → Assistant capability packs (the platform must also enable the matching capability). Common packs include:

Admins can also add and manage data connections in natural language with the help assistant or a work assistant (paste host, database name, account, and so on), not only through forms.

Agents: your dedicated assistant

• Create from a template in the Agent market, or build from scratch (when the current environment treats self-build as the main path, follow the UI);
• In My agents, configure description, knowledge base, memory, operating rules, available data and skills, site embed, and human support;
• Each agent has a stable role and voice, suited to a long-running job assistant (for example HR advisor, compliance Q&A, project aide).

Skill center: teach the assistant how to do it

• View and create workspace skills that describe steps, APIs, and caveats for a kind of task;
• In conversation the assistant can follow a skill to carry out work; skills accumulated in a conversation can be versioned and rolled back;
• You can improve a skill through conversation (draft a revision → preview the diff → confirm and publish);
• Suited to tool-like work such as “check stock”, “export a report”, or “call an API in a fixed sequence”; query-style skills can pair with predefined queries.

Apps: small tools in the workspace

• Open lightweight business tools on the app desktop (simple receiving, a notepad, people-profile style reports, and so on);
• You can also ask an agent in Messages to create an app for you in natural language;
• Change an app’s UI through conversation: stream a revision draft, multi-assistant tabs and a process pane, left–right preview before you confirm, so accidental changes are less likely;
• Members of the same workspace share apps and data, which fits department-scale needs; for complex specialist systems, use plugin apps.

Plugin apps: specialist systems on the workbench

• After you pick a workspace, open Human Resources, Warehouse, Compliance, Email, and similar full modules on the app desktop;
• Tell the app assistant “list departments”, “receive 10 boxes”, “start a check”, “see if there is unread mail”, “write a meeting follow-up”, or “forward this mail to Li”; it acts within your permissions, so you do not have to learn the tabs first. In Email it can also draft the body, a reply, or a forward note to your brief, and send only after you confirm;
• Unlike workspace apps: small tools can be created in conversation; plugin apps are independent specialist systems with their own UI and business data;
• If colleagues still work in legacy HR / OA, embed the assistant in the original page instead; both approaches can coexist.

Workflows: multi-step work you can finish

• In Workflows, create a flow from a template (Simple approval, IWAY factory audit, Blank flow, Employee onboarding), and optionally publish it to the app desktop;
• After you wire nodes on the canvas, colleagues handle work in My todos or on a phone; assignees get a service notification;
• Typical paths: fill an application → a named person approves; or start a check → upload on-site photos for judgment → fix and re-check;
• Can work with plugins: Compliance starts a check that is handled in a workflow; Human Resources can auto-start a handling flow after onboarding, offboarding, or a transfer is completed;
• Image judgment needs a language model that can see images (depends on the current deployment).

Knowledge base: three layers of materials

After you change documents, refresh the index so retrieval follows the latest content.

Embed and platform plugins: AI in your systems

Cadau connects to external business in two typical ways (they can coexist):

1. Host enhancement: embed a Cadau action assistant on an existing HR, OA, or in-house page (lower right, or a designated area)

- People ask the bound agent inside the original system; - The assistant can open a system feature (for example “open the employee profile”), so they switch screens less; - Tokens are issued by the host backend; the browser does not hold a long-lived secret.

1. Plugin apps: after an independent business module is connected, it appears on the Cadau app desktop, adding a specialist capability to one experience (Human Resources, Warehouse, Compliance, Email, Cameras); business rules and approvals still belong to that module.

For integration detail see [sdk/host-embed/网站集成说明.md](/docs/sdk-host-site) and [sdk/host-embed/SDK契约.md](/docs/sdk-host-contract); examples are in examples/hr-multi-tenant/ and examples/henry-iway-compliance/.

---

Typical scenarios

New-hire onboarding

• Write onboarding guides and policy summaries into global and workspace knowledge;
• New hires ask in Messages “How do I take annual leave?” or “What is the expense process?”; the assistant answers from team materials;
• The help assistant covers how to use the product itself; invite and join progress can reach people through service notifications.

A department Q&A assistant

• Admins maintain workspace knowledge and create HR / legal / IT (and similar) role agents;
• Members pick the matching assistant; answers stay consistent and can cite document sources;
• Forms of address and preferences for a person live in memory, not in public knowledge; if the answer is not enough, hand off to human support.

Ask for numbers and charts in conversation

• An admin turns on data connections, sets predefined queries, and authorizes members;
• Members ask in Messages “headcount by department this month” or “make a share chart like this sample”;
• Numbers follow the query result; a sample image is usually layout reference only; if the definition is unclear, the assistant should confirm before producing a formal report.

Project collaboration

• Give the project its own workspace and invite project members;
• Project notes, milestones, and decisions live in knowledge and memory;
• When you need to record or tally, land it quickly with workspace apps, skills, or data connections; if the UI is not right, change the app through conversation.

On-site compliance checks

• Create a check flow from a template in Workflows, and maintain compliance-related knowledge;
• Photograph on site → automatic judgment → fix and re-check; for a full branded capability you can connect a platform-plugin example.

Embedded in a business system

• Embed the assistant on an HR employee profile; the person asks “What are the promotion rules for my grade?”;
• The assistant reads host knowledge plus the Cadau agent configuration, and navigates to a system module to finish the work when needed.

---

Get started in 5 minutes

1. Register or sign in

Use a mobile number or email, with a password or a verification code (the UI defaults to the password path).

1. Start in Messages

With no workspace selected, talk with the help assistant to learn the UI; links in replies can jump in one tap. After you pick a workspace, you can say “generate a skill for me” and similar, and the assistant does it. On other pages you can also open the action assistant in the lower right into the same help conversation.

1. Create or join a workspace

Open Workspace collaboration, create a team space, or accept a colleague’s invite / submit a join request.

1. Create an agent and start talking

Create an assistant in Agents → go back to Messages, pick it → send the first message.

1. Add materials and capabilities as needed

- Shared team notes → workspace knowledge base - Role-specific voice → agent knowledge base - Preferences and decisions about you → “Remember” in conversation, or the agent’s Memory page - Numbers / charts / office documents → ask an admin to turn on the matching assistant capability pack and grant access

Finer steps: [help/new-user-guide/getting-started.md](/docs/help-getting-started).

---

UI entry cheat sheet

A common order on the right of the top bar: Features → Customer service (local seat or support-team member) → Apps → Account → Messages. Other pages may have an action assistant (star) in the lower right, which opens the help assistant with contextual suggested questions.

For external service or Q&A, you can turn on human support for an agent: in conversation the user taps “Human support” to reach a person; see [help/product-features/human-customer-service.md](/docs/help-human-cs).

---

How this relates to other docs

---

FAQ

Do I have to pick a workspace first? No. With no workspace selected you can still use Messages (help assistant), Contacts, Workspace collaboration, and Account. Agents, Skill center, Apps, Workflows, Agent teams, and most assistant capabilities need a workspace selected first.

What is the difference between memory and the knowledge base? A knowledge base is material you write on purpose (policy, process, role voice); memory is about you — preferences, decisions, and project milestones accumulated in conversation. Team materials go in workspace knowledge; personal content goes in memory.

Can colleagues see my conversations? By default, no. Conversations and personal memory are isolated by account; what a workspace shares is team knowledge, apps, skills, authorized data resources, and other explicitly shared resources.

Is it safe to ask about business-database data? Querying a database requires the workspace to have data connections on, plus authorization on data resources / who can use them. Day to day, agree the definition first, then run a predefined query — no SQL assembled on the spot; create/update/delete can require approval. Connection secrets are kept on the server and are not echoed in plaintext in chat.

Do I need to know how to program? For everyday use, no. Creating an app can start from a template; configuring an agent is mainly writing a description and Markdown; you can also improve skills and app UI through conversation. Embedding into an existing system or building a platform plugin is for a development team, following the integration docs.

How is time shown in the UI? Default is Beijing time, Chinese date, 24-hour clock. You can change time zone, date format, and 12/24-hour clock in Account → Preferences → Time display; each user is independent.

Which clients are supported? Web browsers and mobile (exact set depends on the current deployment); the embedded assistant applies to host Web pages.

---

*Version: 1.2 (2026-08-18) · Product capabilities follow* Product specification*; UI and features follow the deployed instance.*