Skip to content
Lenarys Analytics Docs
Back to website
Administration Permissions & security

Permissions & security

Combine Moodle capabilities, the Billing Admin role, report audiences, and definition review.

Capabilities

CapabilityPurposeDefault archetypes
local/la:viewAccess Lenarys Analytics pages and read personal/reporting data exposed there.Manager, course creator, editing teacher
local/la:manageManage Lenarys Analytics reports and administrative workflows.Manager
Grant local/la:view narrowly. It is a system-level capability for an analytics product that can expose personal and course information. Do not assign it to broad learner roles by default.

Role model

Moodle site administrators inherit administrative authority. The selected Billing Admin owns catalogue review, installation, audience, license, and subscription review. Users with local/la:manage can administer the product, while report audiences and enabled state still shape report availability.

SQL review

Reports and apps are definition-driven and can query Moodle tables. Installation validation checks structure, read-only SQL rules, restricted tables, sensitive fields, and supported configuration. Treat these checks as defense in depth.

  • Read every SQL expression, join, dependency, condition, grouping, and alias.
  • Confirm the query returns only fields needed for the report.
  • Prefer Moodle summary tables or plugin rollups over very large event-log scans.
  • Test with a least-privileged user and an out-of-audience user.
  • Re-review generated, duplicated, imported, and updated definitions.

Production hardening

Recommended defaults
API endpoint: trusted HTTPS origin
Debug: disabled
apicurlsettings: []
Learning-time tracking: policy-reviewed
Restricted tables: conservative defaults or stricter
Cron: monitored
Billing Admin: named administrator

Review checklist

  • Review system capability assignments after Moodle role changes.
  • Audit the Billing Admin selection when staff changes.
  • Check report audiences and schedule recipients regularly.
  • Leave technical debug output disabled except during a controlled investigation.
  • Keep Moodle, the plugin, PHP, the database, and mail infrastructure supported and patched.

Was this page helpful?

Your feedback is stored in this browser.