Assign Courier module staff permissions
Grant least-privilege access using the module permission group. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Setup → Staff → Roles → Permissions
Before you start
- Identify the staff role and operational responsibility.
What you’ll accomplish
Grant least-privilege access using the module permission group. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Edit the role.
- Find Courier & Logistics Management.
- Select only the capabilities needed.
- Save the role.
- Sign in as a test user and verify menu visibility and action access.
Fields and options to review
ViewDashboard, registers and read-only pages.
CreateCreate drivers, vehicles, customers, jobs and other supported records.
EditUpdate existing records and operational details.
DeleteUse supported soft-delete actions.
DispatchOpen dispatch and assign eligible resources.
Manage complianceUpload, approve and review driver or vehicle compliance.
Manage financeOpen Finance, settlements, expenses and instant reports.
Manage integrationsOpen Settings, providers, BP fuel and connection tests.
Rules the system enforces
- Administrators pass capability checks automatically.
- A visible menu item does not bypass server-side permission enforcement.
- Finance and Settings are deliberately hidden unless the matching capability is available.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.