Ned Hub

Plugin version: 0.4.5   Compatibility: Moodle 4.5–5.1   Updated: 5 September 2026

Ned Hub (local_nedhub) is the administrator control plane for Ned Tools. It centralizes licence status, Ned Cloud connectivity, cached entitlements, covered usage, the Ned plugin catalogue, and controlled plugin lifecycle actions.

Setup

1. Install or update local_nedhub and complete Moodle's upgrade process.
2. Open Ned Hub settings and configure the Ned Cloud URL and licence key.
3. Validate the licence and refresh entitlement status.
4. Review privacy/data-sharing information before enabling optional lifecycle actions.
5. Use the Plugins page to review approved Ned components and available install/update/uninstall actions.

Expanded-MVP plugin catalogue

The current development catalogue includes Ned Hub, Ned Course QA, Ned Query, Explain Your Thinking, Ned Custom Menu, Ned Profile Enrolment, Ned Grading Assistant, Ned Alerts, Ned Activity Notice, and Ned Cohort Profile Field. The retired local_nedai component is not part of the current MVP catalogue.

Permissions

Lifecycle actions require both moodle/site:config and local/nedhub:manage. Moodle's own capabilities and plugin-manager checks remain authoritative.

Plugin lifecycle

Ned Cloud supplies trust, entitlement, and trusted release metadata. Ned Hub supplies policy, validation, and administrator UX. Moodle performs the actual plugin deployment, database upgrade, dependency/version checks, and uninstall flow.

Install/update validation includes HTTPS release URLs, SHA-256 verification, exact component/version identity, Moodle/PHP compatibility, dependencies, disk space, writable plugin paths, and unrelated pending upgrades. Ned Hub self-update and self-uninstall are excluded.

Privacy and data sharing

Licence validation can send the configured licence key, Moodle site URL/version, aggregate covered student/course counts, and installed Ned plugin metadata to Ned Cloud. Trusted release resolution also sends the requested Ned component with the existing licence/site context.

Package checksum/component validation, plugin discovery, Moodle deployment, database upgrades, and uninstall processing occur locally in Moodle. Plugin lifecycle operations do not require student profile or course-content data to be sent to Ned Cloud.

Licensing

Moodle-side Ned plugins are intended to remain GPL-compatible. Commercial value is provided through Ned Cloud, maintained compatibility, support, documentation, education-specific controls, and hosted services rather than by hiding Moodle plugin source code.

Troubleshooting

• Confirm the administrator has both required capabilities.
• Confirm Ned Cloud and the licence are configured and valid.
• Confirm the component is approved and entitled.
• For updates, confirm the trusted release is newer and disk/database versions agree.
• Resolve unrelated pending Moodle upgrades first.
• Confirm Moodle/PHP compatibility, dependencies, disk space, and filesystem write access.
• Review Moodle/PHP logs before changing multiple settings.

Changed behaviour in 0.4.5

The development catalogue was reconciled with the expanded MVP inventory: Ned Profile Enrolment, Ned Grading Assistant, Ned Alerts, Ned Activity Notice, and Ned Cohort Profile Field are explicit catalogue entries, while retired Ned AI is removed from the current MVP catalogue.