Administration and Controls
How administrators keep Village 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.
- village
- village_home
- village_home_create
- village_home_update
- village_home_delete
- village_resident
- village_resident_create
- village_resident_update
- village_resident_delete
- village_security
- village_incident
- village_incident_create
- village_dues
- village_settings
- village_improvement
- village_violation
- village_amenity
- village_governance
- village_document
- village_report
- village_portal
- village_dues_create
- village_improvement_create
- village_improvement_review
- village_improvement_approve
- village_improvement_delete
- village_violation_create
- village_violation_notice
- village_violation_resolve
- village_violation_delete
- village_amenity_create
- village_amenity_update
- village_amenity_delete
- village_amenity_reserve
- village_amenity_approve
- village_governance_create
- village_governance_update
- village_governance_delete
- village_document_create
- village_document_update
- village_document_delete
- village_document_publish
- village_report_export
- village_announcement
- village_announcement_create
- village_announcement_delete
Settings, Menus, and Configuration
Configuration files found
- default_menu.php
- menu.php
- module_config.php
- permissions.php
- routes.php
- widgets.php
Menu entries found
- Village
- Village Dashboard
- Village Homes
- Village Residents
- Village Improvements
- Village Incidents
- Village Violations
- Village Amenities
- Village Security
- Village Dues
- Village Governance
- Village Announcements
- Village Documents
- Village Reports
- Village Settings
Automation and Integrations
Scheduled jobs
No module-local scheduled jobs were found.
Dashboard widgets
Widget registration or widget helper files were found. Validate source data and visibility.
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: VillageDemoSeeder.php. Use them only for the data purpose documented by the module.
Tests
Module tests found: VillageTest.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.