One organization, one Moodle
An organization is the unit that owns a Moodle connection, its MCP keys, its credits and its subscription. Because a connection is 1:1 with a Moodle install, running two Moodles means running two organizations.
Everything scoped to an organization stays inside it: members of one never see another's keys, usage or conversations.
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including billing, the Moodle connection and deleting the organization. |
| Admin | Manage members, MCP keys and the Moodle connection. No billing ownership. |
| Member | Use the panel and the AI chat. Cannot change the connection or mint keys. |
The distinction that matters day to day: only owners and admins can mint or revoke MCP keys and choose which key powers the AI chat.
Inviting people
Invite from Organization → Members. The invitee gets an email with a link; invitations are valid for 7 days and can be revoked before they're accepted.
An invitation grants access to the panel — it does not create a Moodle account or provision Moodle access. Access to Moodle data always comes from a key, minted from the plugin or the panel, tied to a real Moodle user.
Removing someone
Removing a member revokes their access to the panel immediately. It does not revoke MCP keys they were given — those are separate credentials. When somebody leaves, do both:
- Remove them from the organization.
- Revoke the keys issued to them in Organization → Moodle → MCP keys, and remove their Moodle user from the plugin's Users section.
Switching organizations
If you belong to several, switch from the organization picker in the sidebar. Keys, usage, credits and chat history all follow the organization you're in.
Deleting an organization
Only an owner can delete one. Deleting removes the Moodle connection, the stored encrypted tokens and the keys — assistants stop working immediately. The Moodle web-service tokens themselves live in your Moodle, so remove them there too if you're decommissioning the site.