AI assistant
What the admin dashboard's assistant can answer and do, what it needs to run, and how its models, prompts and tools are set up.
For the Full Stack package
What the assistant does
The admin dashboard has a chat assistant under AI Assistant (/dashboard/ai-assistant). It reads and changes the platform's data for the admin, in plain language. The student site has no assistant.
| Area | What you can ask |
|---|---|
| Courses and categories | List, look up, create, edit, delete and restore. Catalogue statistics. |
| Instructors | Look up, create and edit profiles. Instructor statistics. |
| Enrolments | Who is on which course, enrol a student, change a seat's status. Enrolment statistics. |
| Students and staff | Find people by name, email or username, create and edit accounts, delete and restore them, list staff. |
| Live classes and assignments | List, schedule, move, cancel and delete classes; set, publish and archive assignments. |
| Analytics | Registration figures and trends, drawn as charts in the chat. |
| Settings | Read the site's settings and change one. |
- It acts, not only answers: "enrol this student on that course" finds both and creates the seat. It says so when an action fails rather than reporting it done.
- It works within the admin's own permissions. Anything the admin's role refuses on the screen is refused in the chat too, and the assistant says which permission is missing.
- Images can be attached, up to 6 per message and 10 MB each. The assistant describes them and can use one as a new course's or category's artwork.
- Conversations are saved per admin and listed in the history panel, to reopen, rename, archive or delete.
- Suggested prompts on an empty chat cover the platform overview, this month's enrolments, courses worth promoting and this week's classes.
What it needs
- The API. The assistant runs on the server, so it needs the admin dashboard connected to a running Learnio API.
- An AI provider key. Model calls are paid by a key from an AI provider, set on the API or brought by the admin. Without one, the chat says what is missing instead of failing silently.
- The "Use Assistant" permission. The Super Admin and Admin roles have it out of the box; other roles do not see the menu entry. It opens the chat and its history; what the assistant may do for the admin still follows the admin's other permissions.
Not available on the sample data
The admin dashboard's offline sample data has no assistant: the chat opens with a notice that no model is configured. It works as soon as the dashboard points at an API with a key.
Sample data in the frontendsProvider keys and models
Included with your purchase. Sign in to read, or open it in your download.
Which AI providers and models the assistant runs on, where each key goes, and how an admin can use their own key.
Add a model or a provider
Included with your purchase. Sign in to read, or open it in your download.
The steps to offer another model, or another AI provider, in the assistant's picker.
The prompts
Included with your purchase. Sign in to read, or open it in your download.
Where the assistant's instructions are written and how they are put together for each request.
The tools and how they are wired
Included with your purchase. Sign in to read, or open it in your download.
The 47 tools the assistant can call, how they reach the platform's data, who can use them, and how to add one.
Chat sessions and history
Included with your purchase. Sign in to read, or open it in your download.
Where conversations are stored, who can see them, and the endpoints that manage them.
The demo message allowance
Included with your purchase. Sign in to read, or open it in your download.
How a public demo limits the assistant messages the owner pays for, per visitor and per country.
The MCP module
Included with your purchase. Sign in to read, or open it in your download.
How the assistant's tools are registered as a Model Context Protocol server inside the API.