Understand e-Invoice access and permissions

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Apply the single registered module capability and the admin-only template save/validate gates.

What this guide helps you do

Apply the single registered module capability and the admin-only template save/validate gates. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

1. Grant e-Invoice: Bulk Export only to authorised staff.
2. Use an administrator account to validate and save templates.
3. Retain normal invoice/credit-note permissions for source-record access.

Fields and options

Rules and limits

• The module registers only bulk_export under einvoice_module.
• validate_template_ajax and validate_and_save explicitly require is_admin.
• The template page controller itself is under AdminController; editing an existing ID also verifies type einvoice.
• The output method does not add an explicit document permission check, so protect module/controller access through authenticated authorised roles and normal CRM routing.

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