Create and manage assistants
An assistant is a configured thing, not a chat window. Creating, viewing and managing are separate rights.
/
AI Assistant
AI Assistant is assistants trained on your own material: knowledge bases built from what the business actually holds, a writing assistant inside the editors, and a playground for trying a prompt before it becomes a habit.
Try it in the demoai · 5 tasks
Before you start
- A decision about what material an assistant may be trained on. A knowledge base belongs to a company, and an assistant is only as careful as the material behind it.
- A decision on who may read usage — and, separately, everyone’s conversations.
What AI Assistant does
Assistants trained on your own material.
Train a knowledge base
The knowledge base is what the assistant answers from, and it belongs to a company. Material from one company does not leak into another’s answers.
Use the writing assistant in the editors
It is available where writing already happens rather than as a separate destination.
Try things in the playground
The playground is for working out whether a prompt is reliable before anybody depends on it.
Review usage and conversations
Usage figures and everybody’s conversations are two different permissions. Reading what colleagues asked an assistant is a serious right; grant it narrowly and tell people it exists.
What it claims to do
The capability list this guide is written against, unabridged. Nothing above adds to it.
AI Assistant on the Productivity page- Assistants created, viewed and managed
- Knowledge bases trained
- A writing assistant available in the editors
- A playground for trying prompts
- Usage and — separately — everyone’s conversations
Where it connects
The modules AI Assistant hands work to, or takes it from. Most problems that look like one module are a handover between two.