Understand module assets and route scoping
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Confirm Courier CSS and JavaScript load only on module routes.
Where to goAdmin Area → Courier & Logistics → Any module page
What this guide helps you do
Confirm Courier CSS and JavaScript load only on module routes. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Go to a Courier page and confirm the module layout and interactions load.
- Go to an unrelated admin page.
- Verify the Courier assets do not alter unrelated screens.
Fields and options
This action uses the values already stored on the selected source record. Review that record before continuing.
Rules and limits
- The module head and footer hooks first test whether the current request belongs to the module.
- Asset versions are derived from the deployed file so browser caches can refresh after upgrades.
Check it worked
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.
Related guides
Was this guide useful?Your response is stored only in this browser.