v1.12.0

Kordon 1.12.0

Ever wanted to know what your team has actually been up to in Kordon? Now you can. Kordon 1.12.0 brings User Activity Tracking, much clearer changelogs across the platform, and a handful of important fixes along the way.

— Team Kordon

What's New

User Activity Tracking

You can now open any user's profile and see a full timeline of everything they have done in Kordon: what they created, updated, connected, or removed across every entity they can access.

Each event is shown in plain language with clear authorship and timestamps, and group membership history now shows exactly when users were added to or removed from groups. The result is a reliable audit trail without digging through individual item changelogs or raw system logs.

Clearer Changelogs Across the Platform

Changelog panels on individual records such as risks, controls, assets, and more are now much easier to follow. Events are labelled by what actually happened, not by how the system stored the change, and connection updates appear naturally next to the items they affect.

Safer Credential Audit Trails

API keys and SCIM tokens can now be reviewed safely in activity and changelog views. Secret values are excluded from event payloads so they cannot be accidentally exposed while reviewing history.

Quality of Life

  • Faster Requirements List

    The requirements list now loads noticeably faster, especially in larger frameworks or wherever requirements include rich text content.

Fixed

  • Fixed `regulation_id` in the API body silently doing nothing. Creating a requirement with a framework link now works correctly in one step.
  • Fixed duplicate or empty membership events appearing in the user activity feed.
  • Fixed structured fields and settings showing up as `[object Object]` instead of readable values in changelogs.
  • Fixed API key secret values appearing in changelog targets. Secrets are now properly excluded from event payloads.
  • Fixed risk configuration changes not being recorded in activity history.
  • Fixed some control and requirement connection changes being silently dropped from the event stream.