Understand e-Invoice access and permissions
Apply the single registered module capability and the admin-only template save/validate gates.
Exact navigationAdmin Area → Setup → Staff → Roles; Setup → Settings → Finance → e-Invoice; Utilities → Bulk Export
Before you begin
- 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 covers
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.
Exact step-by-step process
- Grant e-Invoice: Bulk Export only to authorised staff.
- Use an administrator account to validate and save templates.
- Retain normal invoice/credit-note permissions for source-record access.
Fields, choices and supported possibilities
Action scopeApply the single registered module capability and the admin-only template save/validate gates.
Module version1.0.0
NavigationAdmin Area → Setup → Staff → Roles; Setup → Settings → Finance → e-Invoice; Utilities → Bulk Export
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- 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.
Expected result and verification
- 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.