On this page
What Moodle does
Moodle’s AI subsystem connects provider plugins, supported actions and placements inside Moodle LMS. It is not, by itself, a single general-purpose student chatbot. The current Moodle 5.3 documentation covers provider instances, role and activity controls, and a course-level AI usage report. This profile explains those boundaries and proposes a small course pilot; it is based on official documentation, not a live Moodle installation or a provider test.
Where it fits, and where it falls short
Useful strengths
- Provider, action and placement are separate parts of the setup, so administrators can reason about the service connection, function and location independently.
- Provider instances can be configured for different actions, with an administrator-defined order when multiple instances are enabled.
- Site, course and activity settings provide several places to narrow access, while Moodle 5.3 adds course-level visibility into in-Moodle AI actions.
Limits to consider
- The AI subsystem requires administrator setup and a provider plugin or endpoint supported by the site’s Moodle version; a Moodle login alone does not guarantee that AI actions are available.
- Supported providers and controls vary by Moodle version and installed plugins. Check the documentation for the exact version your institution runs.
- Usage reports describe Moodle actions; they are not a detector for outside AI use, a complete academic-integrity record or an invoice.
- Moodle configuration does not make an institution compliant by itself. Provider data handling and local policy need separate review.
A suggested Moodle workflow
View the workflow diagram
- 1
Confirm the Moodle version, the administrator’s plugin permissions and which provider accounts the institution has approved.
- 2
Configure one provider instance and only the actions needed for a specific task; keep its placement disabled until credentials and model settings are checked.
- 3
Pilot the action with permitted course material, test the intended learner and teacher roles, then review the in-Moodle usage report and provider terms before wider access.
Understand the provider, action and placement first
Moodle’s AI subsystem is an integration layer for Moodle LMS. A provider plugin connects the site to an external AI service. An action is a function such as generating text, generating an image, summarising text or explaining text. A placement is where Moodle makes a supported action available, such as the text editor or course assistance. The administrator configures those pieces; installing Moodle does not turn every course into an open-ended chatbot.
The separation matters when a school asks “How do we add AI to Moodle?” Start by naming the task and the part of Moodle where a user should do it. A teacher drafting course content in an editor is a different workflow from a learner asking for an explanation of a course page. The provider plugin also determines which actions it supports, so a model connection does not guarantee every action will be available.
Check your Moodle version before choosing a provider
Moodle’s official release table lists 5.3 as the current stable LTS branch. Its 5.3 provider documentation lists Amazon Bedrock, Anthropic Claude, Azure AI, DeepSeek, Gemini API, Ollama API and OpenAI API. These details are version-specific. Moodle 4.5 introduced the subsystem with OpenAI and Azure provider plugins; do not assume the 5.3 list or later controls are present on an older installation. Confirm the installed Moodle release, supported plugin version and your host’s rules for installing or updating plugins.
Moodle marks its direct Anthropic Claude provider as new in 5.3, and its provider page says that provider does not support image generation. The same page distinguishes it from Amazon Bedrock, which is a separate provider route. Check the actions supported by the exact provider instance you plan to use rather than selecting a provider by model name alone.
Create a provider instance and configure its actions
In the documented 5.3 workflow, an administrator opens Site administration > General > AI providers and creates a provider instance. The administrator chooses a provider plugin and configures the credentials or endpoint details that provider requires. Action settings can be adjusted for the instance, which can remain disabled until it is ready. If multiple instances are enabled, Moodle lets the administrator set their processing order.
Provider instances can use different settings for different jobs. For example, an institution might evaluate a smaller, lower-cost model for a short summary and a different model for text generation. That is a configuration option, not a guarantee that one model is accurate, cheaper overall or suitable for student data. Record which action uses which instance, test an ordinary request and a failure case, and verify the provider’s current account and rate limits before enabling the action.
Budget provider and hosting costs separately
Moodle’s provider documentation lists different account requirements: the OpenAI API provider requires a paid API plan, and the DeepSeek provider requires a paid API key. Those requirements do not establish a single Moodle AI price. Check current provider rates, usage limits, hosting or support costs, and any paid plugin before planning a course rollout.
Moodle’s usage report includes token counts, but it is not a billing report. Compare the Moodle record with the selected provider’s own billing and usage pages; do not treat tokens as a direct estimate of money spent.
Enable only the placement and action the course needs
Moodle’s 5.3 documentation says all AI placements are disabled by default. Administrators enable placements under Site administration > General > AI placements and choose the actions available there. In the text editor, documented actions include Generate text and Generate image. In the Course assistance placement, the actions are Summarise text and Explain text for the main text on a course page.
Users must accept the AI usage policy the first time they use an action. Treat that as one part of the rollout, not a substitute for explaining which provider is configured, what course materials may be sent and where users can find local guidance. Start with one placement and the minimum useful action set; expand only after a teacher has reviewed the interaction.
Supporting documentation: [3]
Review role, course and activity access separately
Moodle documents capabilities for Summarise text, Explain text, Generate image and Generate text at site or course level. Its default Manager, Student, Teacher and Non-editing teacher roles allow these capabilities, so an administrator should not assume that enabling a placement is teacher-only. Roles can be changed at the site level or for a particular course.
Teachers can turn AI tools on or off in a course, then specify which tools are available in an activity’s settings. These course and activity controls are version-dependent; the Moodle 5.1 placement documentation labels them as a new 5.1 feature. For an older Moodle site, check its matching version documentation rather than expecting the same settings. Test with a student-role account and the actual activity before sharing the course.
Read Moodle’s usage report without treating it as a detector
The sitewide report is available to administrators and records how enabled providers were used, including provider, time, token counts, context and users. Moodle 5.3 adds a course-level report: teachers can review student activity in their course, with group visibility affecting which students they can see; students can view their own AI actions.
For a course request, the report lists the provider, action, time, activity, token counts and whether the request succeeded. The prompt and generated content are shown only to the person who made the request; teachers and managers see a summary. This is useful for understanding use of the configured Moodle actions. It does not reveal use of other AI services outside Moodle, decide whether a submission is original, or translate token counts into a provider charge.
Supporting documentation: [4]
Review provider data handling and institutional policy
Moodle describes providers as the connection between its AI subsystem and external AI. The cited Moodle pages do not establish one shared retention, model-training or data-location rule for every provider. Before sending course text or student work, check the provider’s current terms, account tier, configuration and institutional agreement. If a provider offers a locally hosted endpoint, review the server, network and logging setup too; “local model” alone does not verify every part of the data path.
Moodle’s privacy documentation says software tools alone cannot ensure legal compliance: the institution operating the site is responsible for configuring policies and responding to privacy requests. Decide which materials are appropriate for the pilot, communicate the use policy to teachers and learners, and confirm who handles questions or deletion requests. This profile is a setup guide, not legal advice or a privacy certification.
A proposed pilot: check a course-page explanation against its source
This is a proposed evaluation exercise, not a Moodle installation or provider test. Choose a course page whose content the institution permits for the selected provider. Before enabling AI, write down two points a faithful summary must preserve and one misconception the explanation must correct. Enable Course assistance for the pilot, select only Summarise text or Explain text as needed, and restrict the course and activity according to local policy.
Ask a teacher to compare the result with the page and mark any missing qualification or unsupported claim. Then check what a student-role account can access, review the course-level AI usage record and confirm that the report’s visibility matches the course’s group setup. Keep the source, evaluation notes and provider terms together. If the pilot is acceptable, document the chosen provider, action, placement, roles and support route before expanding it.
Separate core providers from Marketplace plugins
Moodle’s core provider list and a third-party Marketplace plugin are different choices. The Marketplace currently lists an OpenAI Compatible API provider plugin as supporting Moodle 5.0–5.3. Its listing describes administrator-configured API keys and endpoints for compatible services. That is one optional provider plugin, not proof that every compatible model works with every Moodle action or hosting plan.
Before installing an add-on, check its supported Moodle versions, maintainer, latest release, permissions, privacy information and required actions on the listing itself. Moodle developer documentation describes providers as interfaces to external AI and explains how provider and placement plugins interact through Moodle’s AI manager. If the need is a full tutoring, course-authoring or automation application, evaluate that specific activity or plugin separately; do not assume the native subsystem supplies it.
Pricing, free access and plan checks
Moodle does not represent one AI provider plan. Provider accounts, usage charges, hosting and third-party plugins are separate decisions. Confirm the current terms and cost for the Moodle host and the exact AI provider before rolling out a workflow.
Confirm billing period, renewal terms, limits and regional availability on the provider’s current plan page before paying.
Questions about Moodle
Does Moodle include AI tools by default?
Moodle LMS includes an AI subsystem, but an administrator must configure a provider and enable a placement. Moodle 5.3 documentation says placements are disabled by default, so users do not automatically receive AI actions just by having a Moodle account.
Which AI providers work with Moodle 5.3?
Moodle’s 5.3 provider page lists Amazon Bedrock, Anthropic Claude, Azure AI, DeepSeek, Gemini API, Ollama API and OpenAI API. Availability differs by Moodle version and installed plugins; verify the documentation and host support for your installation.
Does Moodle’s AI subsystem give students a general chatbot?
Not by itself. The documented actions appear in configured placements such as the text editor and course assistance. A broader tutoring or chat workflow may require a separate plugin or activity.
Can teachers restrict Moodle AI to one course or activity?
Moodle documentation describes course-level AI on/off settings and activity-level tool selection, along with site and course role capabilities. Check your installed version because these controls vary across releases.
Can a teacher see a student’s full AI prompt and response in Moodle?
Moodle 5.3’s course report shows the teacher a summary of a student’s request. The prompt and generated content are shown only to the person who made the request. Students can view their own AI actions.
Do Moodle AI token reports show what the provider charged?
No. Moodle reports token counts and usage details, but the token count is not an invoice. Check the provider’s billing and usage records for actual charges.
Does Moodle guarantee that AI prompts stay private?
No universal provider guarantee is established by Moodle’s setup documentation. Review the selected provider’s terms and configuration, and follow the institution’s data policy before sending course or student content.
Sources and research notes
This guide synthesizes official product information with our editorial assessment of academic use. Suggested exercises are examples you can repeat; they are not results of tests we performed. We do not infer accuracy from a provider’s marketing claims.
- MoodleDocs: AI tools and subsystem overview
- MoodleDocs: AI providers and provider instances for Moodle 5.3
- MoodleDocs: AI placements, actions and access controls for Moodle 5.3
- MoodleDocs: sitewide and course-level AI usage reports
- MoodleDocs: privacy responsibilities for Moodle site operators
- Moodle Developer Resources: AI provider plugin API for version 5.3
- Moodle Marketplace: OpenAI Compatible API provider listing
- MoodleDocs: AI subsystem in Moodle 4.5
- MoodleDocs: AI placements and course controls in Moodle 5.1
- Moodle Developer Resources: current release and support table
Found a changed feature or a factual error? Send the exact page and an official source to info@ai-essay.com. Read our editorial policy for how we handle corrections.