Administration and Controls
How administrators keep App Library secure, configured, and reliable.
Access and Permissions
Start with least-privilege access. Give users only the permissions required for their actual responsibilities, then test using a non-admin account.
- applications
- applications_manage
- applications_releases_manage
- applications_downloads_manage
- applications_review
- applications_reviews_moderate
- applications_analytics
- applications_eu_review
- applications_eu_download
Settings, Menus, and Configuration
Configuration files found
- api_query_filters.php
- api_routes.php
- app_widget_registry.php
- default_menu.php
- euapi_response_schemas.php
- euapi_routes.php
- menu.php
- module_config.php
- permissions.php
- public_pages.php
- routes.php
Menu entries found
- App Library
- Manage Applications
- Categories
- App Library Seo
- Reviews
Automation and Integrations
Scheduled jobs
No module-local scheduled jobs were found.
Dashboard widgets
No dashboard widget registration was detected.
Public pages
Public, portal, guest, or verification routes/configs were detected. Test while logged out.
API surfaces
API config files found: api_query_filters.php, api_routes.php, euapi_response_schemas.php, euapi_routes.php.
Seeders
Seeder files found: ApplicationCatalogSeeder.php. Use them only for the data purpose documented by the module.
Tests
Module tests found: ApplicationsApiTest.php, ApplicationsTest.php.
Administrative Controls Checklist
- The module toggle is enabled only for tenants or environments where the workflow is approved.
- Role permissions are assigned by responsibility, not by convenience.
- Menu entries, default menu entries, and routes point users to the intended module-owned screens.
- Users know who is allowed to change settings, templates, status rules, and delete actions.
- Migrations are applied and table changes are verified in the target tenant context.
- API routes, filters, examples, scopes, and docs are reviewed after any data model change.
- Public pages are reviewed for privacy, accuracy, and brand consistency.
Change Management
- Announce workflow or permission changes before they affect live users.
- Update module README, CHANGELOG, and this guide when a workflow changes.
- For menu, route, permission, widget, API, or migration changes, validate the module from a non-admin account.
- Keep public pages, API examples, dashboard widgets, and scheduled jobs aligned with the real data model.