Understand e-Invoice local-file security | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-e-invoice-local-file-security Publisher: Pixie Technologies LLC Bulk export and operational limitations Understand e-Invoice local-file security Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. This guide explains that the file writer restrictions and complete-write checks. Audience: Server administrators and developers; Permission: Staff login; Module v1.0.0; Where to goAutomatic bulk export → TEMP_FOLDER Before you start - Use an authorised account and confirm the source CRM record or setting is correct. - Follow the exact route shown above; do not force database values to imitate a completed action. What this guide helps you do Know the file writer restrictions and complete-write checks. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Keep the work path under the local TEMP_FOLDER. - Do not pass remote stream URLs. - Check exceptions when a file cannot be created or fully written. Fields and options Action scopeKnow the file writer restrictions and complete-write checks. Module version1.0.0 NavigationAutomatic bulk export → TEMP_FOLDER EvidenceVerify the stored record, status, output, email, event or log produced by the code path. Rules and limits - Only local streams are accepted. - The writer opens in binary mode and treats partial writes as failure. - Shutdown cleanup removes generated working files/directories. Check it worked - The requested record, output or setting is created or updated through the supported module flow. - Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action. - An error message is investigated rather than bypassed. Security, privacy and operational checks - Apply least privilege and verify the correct customer, lead, sales document or recipient before processing. - Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy. - Test configuration changes with controlled records before production-wide use. - Retain or delete evidence only under an authorised retention process. Related guides e-Invoice module overview (https://pixiecrm.com/help-centre/e-invoice-module-overview)Handle no records or template in bulk export (https://pixiecrm.com/help-centre/handle-no-records-or-template-in-e-invoice-bulk-export)Understand e-Invoice version 1.0.0 limitations (https://pixiecrm.com/help-centre/understand-e-invoice-version-1-0-0-limitations)Generate and export an e-invoice (https://pixiecrm.com/help-centre/generate-and-export-an-e-invoice)Send an invoice to a customer (https://pixiecrm.com/help-centre/send-an-invoice-to-a-customer)