Audit Trails in SnapApp™ provide a comprehensive, chronological record of all significant actions taken within the application. This feature allows administrators to maintain high standards of accountability by tracking exactly who created, modified, or deleted specific records across any database object.

Table of Contents

• Accessing Audit Trails
• Types of Audit Data
• Record-Level History
• Configuration and Enablement
• 1. Object-Level Auditing
• Configuring Advanced Audit Logs
• Implementation Steps:
• Managing Audit Data
• Support

Accessing Audit Trails

The Audit Trails interface is integrated into the User Profile menu for quick administrative oversight.

1. Click on your User Profile icon or name in the top-right corner of the global navigation bar.
2. Select Audit Trails from the dropdown menu.

Types of Audit Data

SnapApp automatically captures several layers of activity to provide a comprehensive view of your application’s health:

Record-Level History

Every time a record is created or modified, SnapApp can track the “who, what, and when”. When you open Audit Trails, you are presented with a detailed list of system events. Each entry captures the following critical data points:

• ID: A unique tracking identifier for the specific audit entry.
• Field: Displays the type of action performed, such as Created or Deleted.
• Object: Identifies the database table affected (e.g., translations, departments, or user_groups).
• Record ID: The unique ID of the specific record that was modified or created.
• Old Value / New Value: Provides a comparison of data changes for updates, allowing you to see exactly what information was altered.

Configuration and Enablement

Audit Trails are enabled by default for core system actions such as record creation and deletion. However, administrators can configure more granular tracking through the following methods:

1. Object-Level Auditing

To ensure specific tables are being audited, navigate to Settings > Data > Objects. Within the Object settings, you can verify that the metadata for that object is configured to capture user timestamps (e.g., created_at, modified_by).

Configuring Advanced Audit Logs

While basic tracking is automatic, you can configure more granular audit trails using the Action and Workflow builders.

Implementation Steps:

1. Create an Audit Object: Define a database table specifically for logs (e.g., “system_audit”).
2. Define the Audit Action: Create a DB Insert action that maps the current UserID, Timestamp, and the “Before” and “After” values of a record.
3. Trigger the Log: Attach the action to a DB Upsert workflow so that every change triggers a new entry in your audit table.

Managing Audit Data

• Search and Filter: Use the Search bar in the top-right of the Audit Trails list to find logs for a specific Record ID or Object.
• Exporting Logs: Use the CSV or Print buttons to export audit data for external compliance reporting or security reviews.
• Data Retention: System audit logs are generally stored permanently unless a manual purge is performed by a Super Admin to manage database size.

Support

Thank you for following these steps to effectively manage your SnapApp experience. If you have any questions or need further assistance, please reach out to our support team. We’re here to help you get the most out of your SnapApp experience.

For support, email us at snapapp@bluevector.ai.