Module setup, access and architecture

Assign Delivery Note staff permissions

Grant the least-privilege view, create, edit and delete capabilities registered by the module.

Audience: AdministratorsPermission: Manage staff rolesModule v1.0.0
Exact navigationAdmin Area → Setup → Staff → Roles → Open role → Permissions → Delivery Note

What this guide covers

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.

Exact step-by-step process

  1. Open the relevant staff role.
  2. Find the Delivery Note capability group.
  3. Grant View to staff who need the register, detail, metadata and PDF actions.
  4. Grant Create to staff who may create an invoice-linked note.
  5. Grant Edit to staff who may change an unsigned note.
  6. Grant Delete only to staff authorised to void an unsigned note.
  7. Save the role and test with a representative staff account.

Fields, choices and supported possibilities

  • View
  • Create
  • Edit
  • Delete

Code-backed validations and workflow rules

  • 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.

Expected result and verification

  • The staff member sees only the module actions permitted by the assigned role.

Checks, security 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.