📖 Afaqy Knowledge Base / AVL / Audit Log

<aside> CONTENTS

• Introduction
• Monitoring
• Dashboard
• Reports
• Units
• Messages
• Second By Second
• Tracking
• Multi-Unit Follow
• Users
• Geofences
• Customers
• Resources
• Settings
• Audit Log </aside>

Overview

The Audit Log page provides a complete, immutable record of significant system and user activities within the platform. It is designed to support security monitoring, compliance requirements, operational traceability, and incident investigation.

The Audit Log captures who did what, when, and from where, ensuring transparency and accountability across all actions performed in the system.

Purpose

The Audit Log helps organizations to:

• Track critical user and system actions
• Investigate incidents, misconfigurations, or disputes
• Meet internal governance and external compliance requirements
• Monitor administrative and security‑sensitive activities
• Provide traceability for operational and configuration changes

Scope of Logged Activities

The Audit Log records read‑only historical events. Logged events cannot be edited or deleted by users.

Typical logged actions include (but are not limited to):

User & Access Activities

• Password changes and resets
• Role or permission changes
• User activation, deactivation, or deletion

Configuration & Administrative Actions

• Creation, update, or deletion of:
  • Units
  • Geofences
  • Groups / fleets
  • Alerts and rules
• Changes to system settings
• Assignment or unassignment of units to groups

Operational Actions

• Manual commands sent to units (if applicable)

Page Components

1. Header Information

The header provides basic context for the page:

• Page title: Audit Log

2. Filters Panel

Filters help narrow down log entries for faster investigation. Common filters include:

• User (who performed the action)
• Action type (create, update, delete, login, etc.)
• Module (the target module related to the action)

Multiple filters can be applied simultaneously.

3. Audit Log Table

The main section displays audit events in a structured table.

Typical columns include:

• Date / Time
• User (account that performed the action)
• Action (type of operation performed)
• Module (target module)
• Details (summary of what changed)

Table behavior:

• Sorted by most recent events first by default
• Supports pagination

Retention

Audit logs are retained according to system or tenant-level retention policies. Older records may be archived or purged automatically based on configuration.

Access Control

Access to the Audit Log is permission-based and can be granted to different user types, including client users. Visibility is scoped so users only see audit entries relevant to their allowed scope.

Best Practices

• Regularly review audit logs for unusual or unauthorized activity
• Use filters to isolate specific incidents or users quickly
• Export logs when required for compliance audits or investigations
• Treat audit data as read‑only and authoritative