Audit Logging

MQUAD maintains a comprehensive audit log of all significant actions across the platform, providing a complete traceability trail for compliance, security, and operational review.

Audit Log Overview

Access the audit log from Workspace Settings > Audit Log. The log displays a chronological list of events with:

• Occurrence Time — Exact date and time of the action
• Actor — Email of the user who performed the action
• Action — Dot-notation event code (e.g., survey.published, user.deleted)
• Resource Type — The type of object affected (survey, user, response)
• IP Address — The originating IP address

The audit log is stored in a dedicated immutable database and is accessible to users with specific administrative permissions.

Event Taxonomy

Audit logs capture events using a hierarchical dot-notation:

Survey Events

• survey.created — A new survey definition was created
• survey.published — A survey was made live for collection
• survey.closed — Collection was stopped for a survey
• survey.deleted — A survey was removed from the system

User & Permission Events

• user.invited — A new user was invited to the workspace
• user.deleted — A user access was revoked
• permission.assigned — A role or permission string was modified

Response Events

• response.submitted — A new submission was received
• response.approved — A response passed validation/review
• response.deleted — A specific response was removed

System Events

• tenant.suspended — Access to the entire workspace was blocked
• export.created — A data export job was initiated

Searching and Filtering

Use the audit log interface to find specific events:

1. Action Filter — Filter by specific event codes (e.g., survey.* for all survey actions)
2. Actor ID — Find actions performed by a specific user (UUID)
3. Date Range — Define the start and end window for the search
4. Resource ID — Find all actions taken against a specific object

Exporting Audit Logs

Administrators can export audit logs in CSV or JSON format for external compliance reporting. Note that large exports are processed asynchronously to maintain system performance.