Administration and Controls
How administrators keep Lending 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.
- lending
- lending_create
- lending_update
- lending_delete
- lending_products_manage
- lending_approve
- lending_disburse
- lending_payments
- lending_payments_reverse
- lending_collections
- lending_reports
Settings, Menus, and Configuration
Configuration files found
- default_menu.php
- menu.php
- module_config.php
- permissions.php
- public_pages.php
- routes.php
- settings_lists.php
- system_logs.php
Menu entries found
- Lending
- Lending Dashboard
- Lending Applications
- Lending Borrowers
- Lending Loan Accounts
- Lending Repayments
- Lending Collections
- Lending Products
- Lending Reports
- Lending Settings
Automation and Integrations
Scheduled jobs
1 job(s) found. Review cron, job setting gates, and last-run evidence.
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
No API config files were detected.
Seeders
Seeder files found: LendingDemoSeeder.php. Use them only for the data purpose documented by the module.
Tests
Module tests found: LendingCalculatorTest.php, LendingTest.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.
- 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.