Report library

Manage installed reports, personal report state, apps, and catalogue items from one workspace.

Library tabs

Reports

Installed reports available to the current user under audience rules.

Apps

Installed dashboard-style apps and their current enabled state.

Marketplace tab

The Lenarys Analytics report and app catalogue. Visible only to the Billing Admin and separate from Moodle Marketplace.

Installed reports

The Reports tab supports server-side search, sortable metadata, pagination, favorite state, enable/disable state, and item actions. A report can be installed globally while still disabled for one user.

Access and enabled state are different. Audience rules decide whether a user may use a report. The user-report relation stores whether that user enabled it, favorited it, and customized its parameters.

Report actions

Action	Result	Typical access
Favorite	Adds the report to the user’s favorites.	Report user
Show / hide	Changes the user or managed report state.	Varies by context
Edit details	Changes name, description, and tags.	Billing Admin
Duplicate	Creates an independent copy for customization.	Authorized manager
Reset	Restores the report definition or user customization.	Authorized manager
Uninstall	Removes the installed report and related plugin records.	Billing Admin

Catalogue review

Installing from the catalogue is intentionally a review workflow. The modal can show report or app details, definition metadata, SQL snippets, validation results, configured columns or widgets, preview rows, version, and required plan.

Confirm the purpose
Make sure the grain and intended audience match the business question.
Review every SQL snippet
Confirm tables, joins, filters, selected fields, and aggregation scope.
Check the preview
Look for duplicate rows, unexpected personal data, and missing constraints.
Install only after approval
Validation is a guardrail; human SQL and privacy review remain required.

Plan locks

Installed items remain installed after a plan change, but premium execution is checked against the current entitlement. A locked report or app should be left visible enough to explain the required plan while its execution and background delivery stay unavailable.

Was this page helpful?

Your feedback is stored in this browser.