Assign Delivery Note staff permissions
Grant the least-privilege view, create, edit and delete capabilities registered by the module. 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 → Open role → Permissions → Delivery Note
What you’ll accomplish
Grant the least-privilege view, create, edit and delete capabilities registered by the module. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Go to the relevant staff role.
- Find the Delivery Note capability group.
- Grant View to staff who need the register, detail, metadata and PDF actions.
- Grant Create to staff who may create an invoice-linked note.
- Grant Edit to staff who may change an unsigned note.
- Grant Delete only to staff authorised to void an unsigned note.
- Save the role and test with a representative staff account.
Fields and options to review
- View
- Create
- Edit
- Delete
Rules the system enforces
- Every admin controller action runs the matching capability guard.
- Unauthenticated staff are redirected to the admin authentication page.
- Delete is used for the void action; the module does not hard-delete an individual delivery note through the controller.
- Administrators should still use least privilege even where the CRM grants broad administrator access.
How to confirm it worked
- The staff member sees only the module actions permitted by the assigned role.
Safety checks and troubleshooting
- A missing menu can be a permission issue rather than an installation failure.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.