Skip to main content

Audit Log

The Report Forge audit log records every action taken on blueprints, editions, outputs, and workspace configuration. It is the authoritative record for compliance reviews, dispute resolution, and security investigations.

Access: Workspace Settings → Audit Log (Workspace Admin only).

What is logged​

Blueprint events​

EventFields recorded
Blueprint createdUser, timestamp, blueprint name
Blueprint design changedUser, timestamp, changed field/section (summary)
Blueprint publishedUser, timestamp, version number, version note
Blueprint archivedUser, timestamp
Blueprint restoredUser, timestamp
Blueprint deletedUser, timestamp

Edition events​

EventFields recorded
Edition createdUser, timestamp, edition name, blueprint
Edition data savedUser, timestamp, section modified, field count changed
Edition submittedUser, timestamp
Edition recalledUser, timestamp
Edition comment addedUser, timestamp, comment level (field/section/edition), field path
Edition changes requestedUser, timestamp, open comment count
Edition resubmittedUser, timestamp
Edition approvedUser, timestamp
Edition closedUser, timestamp
Edition assignee changedUser, timestamp, old assignee, new assignee
Edition re-openedUser, timestamp, from status

Output events​

EventFields recorded
Output generatedUser, timestamp, output template name, format
Output downloadedUser, timestamp, format
Scheduled export completedTimestamp, format, delivery status
Scheduled export failedTimestamp, error code

Access and team events​

EventFields recorded
Member invited to projectInviting user, timestamp, invited email, role
Member role changedUser, timestamp, changed member, old role, new role
Member removed from projectUser, timestamp, removed member
Member added to workspaceUser, timestamp, email
Member removed from workspaceUser, timestamp

Configuration events​

EventFields recorded
Workspace settings changedUser, timestamp, setting name, old value, new value
Data connection createdUser, timestamp, connection name, type
Data connection credentials updatedUser, timestamp
Data connection deletedUser, timestamp
API key createdUser, timestamp, key name, scope
API key revokedUser, timestamp, key name
Notification settings changedUser, timestamp

Viewing the audit log​

Workspace-level log​

  1. Go to Workspace Settings → Audit Log.
  2. The log shows all events across all projects in the workspace, newest first.
  3. Use filters to narrow results (see below).

Project-level log​

  1. Open a project → Project Settings → Audit Log.
  2. Shows only events for this project's blueprints and editions.

Edition-level activity log​

  1. Open any edition → Activity log (right panel).
  2. Shows the lifecycle and comment history for this specific edition.
  3. This is the primary view for reviewers and contributors — the workspace audit log is for admins only.

Filtering the audit log​

FilterOptions
Date rangeFrom / To date picker
Event typeBlueprint, Edition, Output, Access, Configuration (multi-select)
UserFilter by specific user name or email
ProjectFilter by project (workspace-level log only)
BlueprintFilter by blueprint name
EditionFilter by edition name
StatusSuccess / Failed (for output and sync events)

Combine filters: date range + user + event type is the most common combination for security reviews.

Exporting the audit log​

  1. Apply any required filters.
  2. Click Export → CSV.
  3. The CSV contains all visible log entries with full field details.

CSV columns: Timestamp, Event type, User, User email, Project, Blueprint, Edition, Detail, IP address (if enabled)

The CSV is suitable for import into Excel, Splunk, or other log analysis tools.

note

Audit log exports are limited to 50,000 rows per export. For larger date ranges, export in segments (e.g. monthly exports).

Common audit scenarios​

Scenario 1 — Who approved a specific edition?​

  1. Go to Audit Log.
  2. Filter: Event type = Edition, Event = "Edition approved".
  3. Search for the edition name.
  4. The log shows the approving user, their email, and the timestamp.

Scenario 2 — What changed in an edition before approval?​

  1. Open the edition → Activity log.
  2. Filter by Data changes.
  3. The log shows which sections were modified, how many fields changed, and by whom.

Scenario 3 — Was an edition approved without a reviewer change?​

  1. Filter audit log: Event type = Edition, user = the contributor (not a reviewer).
  2. Look for a sequence: submitted → approved where the approving user is the same as the submitting user.
  3. This indicates self-approval — a governance violation if your policy requires separate reviewer approval.

Scenario 4 — Who accessed a confidential edition?​

  1. Filter: Event type = Edition, Event = "Output downloaded" OR "Edition data saved".
  2. Filter by the specific edition name.
  3. Review all users who accessed the edition.

Scenario 5 — When was a blueprint structurally changed?​

  1. Filter: Event type = Blueprint, Event = "Blueprint published".
  2. Filter by blueprint name.
  3. Each publish event shows the version number and the version note entered by the designer.

Data retention​

Log typeRetention period
Edition eventsRetained indefinitely (linked to edition record)
Blueprint eventsRetained indefinitely
Access eventsRetained for 3 years (default)
Configuration eventsRetained for 3 years (default)
Output eventsRetained for 3 years (default)

Retention periods can be configured for compliance requirements. Contact Kazinex support to adjust retention settings beyond the defaults.

Privacy considerations​

The audit log records user identities (name and email) for all actions. This is necessary for accountability and compliance.

Access controls:

  • Only Workspace Admins can view the workspace-level audit log.
  • Project Admins can view the project-level audit log.
  • Standard members (contributors, reviewers) can view the edition-level activity log for editions they are assigned to — they cannot see who performed actions they were not involved in.

Data subject requests: If a member requests deletion of their personal data (right to erasure under privacy regulations), the audit log entries cannot be deleted — they form part of the accountability record. The member's email and name may be anonymised in the log upon request, subject to Kazinex's data processing agreement.

What's next​