Embed in existing systems
People stay signed in to the system they already use. The assistant shows up as part of it.
Many teams already run HR, OA, or internal systems. Cadau has two typical paths. They can coexist.
1. On the page you already use
Place an action assistant on an existing page (corner or a reserved area). Colleagues do not each need a new Cadau account just to ask. The assistant can open a system screen — for example “open this employee file”.
Tokens are issued by the host server. The browser does not hold a long-lived secret.
2. As a specialist module on the workbench
A specialist module can appear inside the Cadau workbench. Compliance and approval stay with that module. The user-facing guide is plugin apps.
Which path fits
| Your situation | Better fit |
|---|---|
| People already work in a legacy system | Embed on the page |
| You want chat, knowledge, and apps in one workbench | Plugin apps |
| You need both | Do both |
Integration is work for the developing team, following the integration docs. On the product side, decide first: which page the assistant appears on, which voice it uses, and which data it may see.
Related: What the assistant can do · Blog: Embedding Cadau in a legacy system