Understand void-action visibility and permission | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-void-action-visibility-and-permission Publisher: Pixie Technologies LLC Register, editing and status control Understand void-action visibility and permission Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Distinguish the implemented controller capability from the buttons actually present in the supplied UI. Audience: Administrators and implementation teams; Permission: Manage roles and Delivery Note: Delete; Module v1.0.0; Where to goAdmin Area → Setup → Staff → Roles → Delivery Note → Delete What this guide helps you do Distinguish the implemented controller capability from the buttons actually present in the supplied UI. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects. Follow these steps - Grant Delete only to approved roles. - Check the supplied admin view and confirm no Void button is displayed. - If the organisation exposes the controller action, add it only through an approved scoped implementation with confirmation and CSRF protection. - Test that signed notes remain protected. - Document the deployed interface accurately. Fields and options - Delete capability maps to void controller - No hard-delete controller - No visible void button in supplied detail/list views - Signed status remains non-voidable Rules and limits - The Help Centre must not invent a visible path that the module does not implement. - Capability existence does not prove a button exists. - Any later UI addition should preserve the model’s signed lock and audit event. Check it worked - Administrators understand the real code possibility without misleading staff about current UI. Safety checks and troubleshooting - Treat this as a technical action reference, not a standard clickable user workflow in the supplied build. 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 Review the Delivery Note compliance event log (https://pixiecrm.com/help-centre/review-the-delivery-note-compliance-event-log)Void an unsigned Delivery Note (https://pixiecrm.com/help-centre/void-an-unsigned-delivery-note)Understand the signed Delivery Note lock (https://pixiecrm.com/help-centre/understand-the-signed-delivery-note-lock)Browse all Delivery Note guides (https://pixiecrm.com/help-centre/category/delivery-note)