Dashboard, queue and audit

Review an EmaraTax audit trail

Follow this guide to use the stored actions, details, staff ID, IP and timestamps to reconstruct module activity. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: EmaraTax eInvoicing: ViewModule v1.0.0
Jump to steps
Where to goAdmin Area → EmaraTax eInvoicing → Open document
Before you start
  • Use the exact navigation above and confirm the intended record, tenant, customer, property, document or date range.
  • Verify module activation and the stated permission instead of using another staff member’s account.
  • For public, email, provider, finance, signature or destructive actions, use a controlled test record before production use.

What you’ll accomplish

Use the stored actions, details, staff ID, IP and timestamps to reconstruct module activity. These instructions follow the supplied module’s live menus, controller actions, form fields, model validation and downstream effects.

Follow these steps

  1. Sign in to the staff admin area and open Admin Area → EmaraTax eInvoicing → Open document.
  2. Verify that your account meets the access rule: EmaraTax eInvoicing: View.
  3. Go to the required record or configuration and review its current values before making a change.
  4. Complete the displayed fields or action exactly as described in this guide.
  5. Save, submit, download or confirm the action using the button presented by the module.
  6. Reopen the source record and verify the expected status, output, notification, file or linked record.

Fields and options to review

Common actionscreated, validated, opened and workflow-specific events
EvidenceStaff ID, IP address, details and created time
Category/help-centre/category/emaratax-einvoicing/
Topic/help-centre/topic/emaratax-einvoicing-dashboard-audit/

Rules the system enforces

  • Credit-note compliance page access records an opened event when a document exists.
  • Audit records are module evidence and should follow the organisation’s retention policy.

How to confirm it worked

  • The review an emaratax audit trail workflow completes without bypassing the module’s permission and validation checks.
  • The saved value, generated file, status, notification or linked CRM record is visible from the same workspace.
  • Any validation message remains visible until the source data or setting is corrected.

Security, privacy and operational checks

  • Use least-privilege staff access and do not use another person’s account to reach a hidden action.
  • Check personal, financial, identity and compliance data before sending, exporting or exposing it through a public link.
  • Test configuration, email, public forms, accounting effects and provider connections with controlled records before production-wide use.