Skip to content

Audit Trail ​

Audit readiness depends on traceability: who did what, when, why, and with which Evidence. In Modulos, two surfaces give traceability:

  • Notifications help users do their work and work together.
  • Comments and Logs keep the audit trail of each object.

What this is ​

The sections below tell how to use the audit trail of Modulos:

  • where to find it
  • who can see what
  • how it helps Reviews, decisions, and audits

Where in Modulos ​

Members of an AI System can see most of the audit trail of that AI System. Organization Admins and AI System Owners manage the access.

  • Notifications (the bell in the page header) for your personal inbox of assignments and other events
  • AI System → Overview → Comments and Logs for the log of the AI System itself
  • the Comments and Logs tab of a Control, a Requirement, or an Asset for the history of that object. Policies and policy versions in Policy Center have the same tab.
  • Organization → Notifications → Audit Log for the log of changes to the notification settings (less than its name says, see below)

Who can do what ​

Permissions

  • Each user sees only their own notifications.
  • All members of an AI System can see the Comments and Logs of its objects, and they can add comments. While an Asset is not In Progress, nobody can add a comment to it.
  • Viewers read the AI System and add comments, but cannot change items. They use the logs to examine traceability.
  • Organization Admins and AI System Owners manage the access. They set who can see which trail.

How it works ​

Notifications ​

Each user gets personal notifications. Modulos makes them for changes such as:

  • Review requests and their decisions
  • assignments and changes of owners
  • status changes of important objects
  • comments and mentions, and failed tests

Each notification has a tag in your language, for example Assigned, Review assigned, Status changed, or Mentioned. Notifications help you find what needs work. They are not the audit trail.

Notifications page with All and Unread tabs, a Search field, an unread counter, and notifications with tags such as Mentioned and Status changed.

Notifications are your personal queue of Review requests and other events. Select a notification to open its object. If Modulos has no link to the object, the notification only becomes read.

  1. Unread Shows only the notifications that you did not read.
  2. unread notifications Shows how many notifications you did not read.
  3. Mentioned Each notification has a tag. It opens the object of the change if Modulos has a link to it.
  4. Mark as read Mark the selected notifications as read, or delete them.

Notification channels ​

Modulos sends notifications on two channels:

  • In-App: the platform inbox above. It is always on.
  • Email: an Organization Admin sets it on or off for all of the organization in Organization → Notifications → Channel Settings, and then selects Save.

Choosing what you receive ​

Each user selects the notifications that they get by email in User Profile → Settings → Notifications. This Notification Preferences page has a matrix of categories with In-App and Email switches. In-App is always on. For required notification types, Email is also always on. To keep your changes, select Save Changes.

When email notifications are off for the organization, the Email column is not there, and a notice tells you that email notifications are off. To get them, speak to an Organization Admin.

The Audit Log tab ​

Organization → Notifications also has an Audit Log tab that organization members can see. This tab is a log of settings, not the audit trail of your governance work. It records the changes to the notification configuration of the organization, for example who set email notifications on or off, and when.

For the history that Reviews and audits use, go to the Comments and Logs of each object, as described below.

Comments and logs ​

Controls, Requirements, Assets, and AI Systems have a Comments and Logs tab. This tab shows, with the newest entry at the top:

  • each change, with its date and time
  • the user who made each change
  • comments that tell why a user made a change

This is the primary audit trail for auditors.

Each object logs its own changes. A Control logs its status changes, its Owner, its Evidence, and its tests. A Requirement logs its status, its Owner, and when it becomes ready for review.

Comments and Logs tab of a Control with a comment editor and log entries with users and times.

Comments and Logs keep the history that auditors use: the actions, the time stamps, and the comments that tell why.

  1. Comments and Logs The history of this object.
  2. Comment Add a comment to tell why you made a change.
  3. Comments and Logs Each entry records a change, the user, and the time.

Mentions in comments ​

In the comment editor of Comments and Logs, type @ to mention an item or a user. Modulos first asks for the type of item, then for the item:

  • In an AI System (Controls, Requirements, Assets, and the AI System Overview), the types are Control, Evidence, Framework, Requirement, Risk, Risk Threat, Risk Category, Test, User, and Policy. Agent Test is also a type when your organization uses Agent Tests and you can read them.
  • On a Policy and on a policy version, the types are Policy, Risk Category, Risk, Risk Threat, and User.

A mentioned item becomes a link in the comment. A mentioned user gets a Mentioned notification, if the user is an active member of the AI System or of the organization. The author of the comment gets no notification. In a posted comment in an AI System, Modulos also makes links from the codes that you type, for example MCF-24 or E-12.

To stop the emails for mentions, open User Profile → Settings → Notifications. The Collaboration group has one row for each place: Control mention, Requirement mention, Asset Card mention, AI System mention, Policy mention, and Policy Version mention. In-app notifications are always on.

The log of an AI System ​

The Comments and Logs tab on the Overview of an AI System is the log of the AI System itself. It records these changes:

  • the creation of the AI System and changes to its details
  • frameworks that a user adds
  • risks, Evidence, and Sources that a user adds or removes
  • owners that a user adds or removes
  • changes to the EU AI Act settings and the results of the EU AI Act questionnaire
  • changes to the registration status

When an Organization Admin or a Registration Manager rejects a registration, the text that tells why becomes a comment on this tab.

AI System Overview, Comments and Logs tab, with log entries for Evidence, Sources, registration status changes, frameworks, and the creation of the AI System.

The Overview of an AI System has its own log: creation, frameworks, Sources, Evidence, risks, owners, EU AI Act settings, and registration decisions.

  1. Comments and Logs The log of the AI System itself.
  2. Comments and Logs Changes of the registration status, with the user and the time.
  3. Comments and Logs Sources, Evidence, risks, and owners that users add or remove.

How they connect ​

One change can make two records: a log entry on the object, and a notification for the assignee, the owner, or the reviewer. The two records have different jobs:

RecordWhereWho sees itYou can delete itJob
NotificationThe bell in the page headerOnly the user who gets itYesYour queue of work
Log entry or commentThe Comments and Logs tab of the objectEach user who can open the objectNoThe audit trail

When a user deletes an AI System, Modulos also deletes the Comments and Logs of the AI System and of its objects.

How to use it ​

  1. Work from your inbox Use notifications as your queue of Review requests and assignments.
  2. Open the object Go from the notification to the Control, the Requirement, or the Asset.
  3. Add context Write comments that tell why you made a decision.
  4. Make Review decisions Select Approve or Reject on an Asset Review when you are the reviewer.
  • Follow the history: use the logs to see what changed, who changed it, and when.

Important considerations ​

  • You see only the logs of objects that you can open. If you cannot see a trail, examine your AI System access.
  • For audit readiness, tell your teams to write the cause in a comment when they make an important change.