Skip to content
Moltaro Docs

History and audit

History and audit help users trust a record. They answer questions such as what changed, who changed it, when it changed, and which surrounding event explains the change.

The exact history available depends on the record type, enabled features, access rules, retention settings, and the workflow that produced the change.

Activity, history, and audit

Section titled “Activity, history, and audit”

These words are related, but they are not identical.

Activity is the user-facing stream of notable events around a record or related workflow. It helps people catch up quickly.

Record history focuses on changes to the record, such as field updates, assignment changes, comments, files, tags, or lifecycle events when those areas are tracked.

Audit information is the governed evidence used to explain important changes. It is especially important for access changes, business facts, responsibility, and process-sensitive operations.

What history can show

Section titled “What history can show”

Depending on configuration and access, history may include:

  • field values before and after a change;
  • who created or updated a record;
  • when a change happened;
  • assignment or responsibility changes;
  • comments, file, or tag events;
  • archive or restore events;
  • actions, workflow, board, or module events linked to the record.

History is most useful when the record type has meaningful fields and clear responsibility. A good record should explain both its current state and the path that led there.

Access-aware history

Section titled “Access-aware history”

History follows access rules. A user may be able to open a record but not see every field value that changed. Sensitive fields, restricted linked records, or security-related details may be hidden or summarized depending on the user’s permissions.

This keeps audit useful without turning history into a side door for restricted data.

Retention and expectations

Section titled “Retention and expectations”

Not every record type keeps the same history forever. Some record types may have audit enabled with long retention. Others may keep less detail because the business object is simple or the organization has different retention rules.

When auditability is important, administrators should configure the record type so important changes are structured, tracked, and visible to the right roles.

Where to go next

Section titled “Where to go next”