Audit Logging

Overview

An audit log is a trail that shows who changed what and when on the platform. When a record is created or updated, or an action takes place, the platform quietly notes who did it and when. This trail matters for team accountability: when you wonder why a piece of data changed, it gives you a reliable source you can look back on.

This feature is an evolving area. Today the platform keeps, at the infrastructure level, when and by whom each record is created and updated — so the basic audit information is already being collected. The screens that will present this information with rich capabilities such as search, filtering and export are planned and on the development roadmap. We prepared this document to describe honestly where the feature stands today and where it is heading.

Once complete, the audit trail will be a powerful tool for security, compliance and troubleshooting. Tracing the source of a change, noticing an unauthorized action, or understanding when a problem started all become possible thanks to these records.

Who uses it

• Organization administrators: Review the record of important changes made in their organization to track what changed and when. They use this trail for accountability and trust.
• Compliance and security officers: Verify who performed specific actions for regulatory compliance and internal auditing. They are the heaviest users of the audit trail.
• Support and operations teams: While investigating the root of a problem, look at the history of the relevant record to understand what changed and when.

Step-by-step process

The steps below describe the general flow you will follow once the feature is fully available. Today the basic audit information is collected in the background, and the screens that present it will be rolled out gradually.

1. Access the audit records. When you have permission, you will be able to view an organization’s activity feed or the change history of a specific record.
2. Review a record’s history. You will see how a particular item changed over time, along with when and by whom each change was made.
3. Filter the records. You will quickly reach the event you are looking for by narrowing down by date range, user or action type.
4. Follow the activity feed. You will be able to track the latest actions across the organization as a chronological feed.
5. Export. You will be able to export the audit records for reporting or archiving purposes.

For today, the creation and update information of each record (when, by whom) is already kept; the viewing and search capabilities above are the next steps on the roadmap.

Process flow

flowchart TD
    A[A user performs an action] --> B[The platform records it in the background]
    B --> C[Who and when is kept]
    C --> D{Is the viewing screen ready?}
    D -- Today --> E[Basic information is stored in the infrastructure]
    D -- Roadmap --> F[Search, filtering, export]
    F --> G[Administrator reviews the audit trail]

Frequently asked questions

Is audit logging fully working right now? Partly. The platform already keeps, at the infrastructure level, when and by whom each record is created and updated. The screens that present this information with capabilities like search, filtering and export are on the development roadmap and will be rolled out gradually.

What does the audit trail record? Fundamentally, when and by whom a record was created, and when and by whom it was last updated. In later stages, details such as which field changed from which old value to which new value are also planned.

Who will be able to access this information? Primarily organization administrators and compliance and security officers. Since the audit trail is a sensitive record, access will be limited by permission.

How long will records be kept? The policies for retention are in the planning stage. The goal is to balance both compliance and performance by regularly archiving or clearing old records.

Will I be able to see whether I changed a record or someone else did? Yes, that is exactly the goal of the feature. Because who made each change is kept, you will be able to see the source of a change by looking at a record’s history.

When will this feature be complete? We are not sharing a firm date, but since the basic infrastructure is ready, the viewing and search screens will be added gradually. Progress will be announced with product updates.