Understand the Delivery Note menu and exact routes | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-the-delivery-note-menu-and-exact-routes Publisher: Pixie Technologies LLC Module setup, access and architecture Understand the Delivery Note menu and exact routes Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Map the visible sidebar entry and supported admin, public and client-PDF endpoints. Audience: Administrators and technical support; Permission: Delivery Note: View; Module v1.0.0; Where to goAdmin Area → Delivery Note What this guide helps you do Map the visible sidebar entry and supported admin, public and client-PDF endpoints. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects. Follow these steps - Use the sidebar Delivery Note entry to open the register. - From an invoice, use the injected Create/View Delivery Note action. - Use clean admin controller actions for create, edit, view and PDF. - Use the secure recipient link generated by the module rather than constructing a token URL manually. Fields and options - Admin register: `/admin/delivery_note` - Invoice resolver: `/admin/delivery_note/invoice/{invoiceId}` - Create/edit/view/PDF/invoice metadata/void controller actions - Public view/sign routes using the secure token - Client invoice PDF route with invoice ID and hash - Hyphenated compatibility aliases - Sidebar icon: Font Awesome truck - Sidebar position: 46 Rules and limits - The live module defaults to underscore routes because the target SaaS router recognises them reliably. - Compatibility aliases exist, but the helper validates configured public routes and falls back when a value is unsafe. - The `dead_public_*` controller methods are not active user workflows and are excluded. Check it worked - Support staff can identify the correct code-backed destination for each action without inventing a menu path. Safety checks and troubleshooting - Never expose a secure token in a public article, ticket screenshot or shared log. 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. Related guides Understand module enabled and invoice UI options (https://pixiecrm.com/help-centre/understand-module-enabled-and-invoice-ui-options)Assign Delivery Note staff permissions (https://pixiecrm.com/help-centre/assign-delivery-note-staff-permissions)Understand Delivery Note reference numbering (https://pixiecrm.com/help-centre/understand-delivery-note-reference-numbering)Browse all Delivery Note guides (https://pixiecrm.com/help-centre/category/delivery-note)