Skip to main content

Audit Log

A safety net and insurance for your company

Ellen Rydberg avatar
Written by Ellen Rydberg
Updated this week

The Audit Log is an add-on service in Cinode, available only to administrators. Contact us for more information.

The Audit Log provides transparency into critical actions performed within your Cinode environment. It helps administrators track key events such as deletions, exports, and user changes. This functionality ensures accountability and acts as an insurance policy for your organisation by showing what happened, when, and by whom.


Why the Audit Log Matters

Certain actions—such as deleting important data—cannot easily be reversed or detected without proper logging. With the Audit Log, administrators can:

  • See when sensitive actions have occurred.

  • Identify which user performed the action.

  • Increase security, traceability, and compliance.


What the Audit Log Records

The Audit Log can capture the following actions:

  • Export projects

  • Export customers

  • Export customer contacts

  • Delete customer

  • Delete customer contact

  • Delete project

  • Delete role

  • Delete user profile

  • Delete user CV

These encompass both export-related events (client-side data extractions) and deletions of various entity types within the system.

  • Source – where the action was performed: App, API, or Admin.

  • Period – the date and time when the action occurred (with the option to filter by a start and end date).


How to Use the Audit Log

  1. Navigate to the Audit Log

    • Go to Administration → Company → Audit Log.

  2. View Actions

    • Each entry includes the user, the action performed, the source (e.g. App or API), and the timestamp.

    • For example: “Fredrik Isaksson: deleted CV Project Manager (Jessica Kowalski)”.

  3. Filter Actions
    Use the filters at the top to quickly narrow down relevant entries:

    • Action type – Filter by any of the actions listed above.

    • Source – Choose between App or API.

    • Period – Set a start and end date to restrict the timeframe.

    • Query – Search by object name (e.g. project title, user) or the performing user’s name.

  4. Export Results

    • Apply filters first, then export the filtered list for audits, compliance checks, or internal documentation.


Tip:

Before exporting, refine your search with filters to reduce large datasets and make the result more meaningful and manageable.

Did this answer your question?