Audit log

The audit log is an append-only record of every change made to a project’s data. In normal use nothing in it is edited or removed — there is no edit or delete action anywhere in the app; every entry is written automatically when a change happens. Use it to answer “who changed this, and when?” — including changes made by the AI.

Find it in the project sidebar under Audit log. You need read access to the project to see its history: if you can’t open the project, you can’t see its log.

What you see

The log shows you the entries about things you can open yourself. If a risk, an email, a document or anything else is restricted so that you can’t open it, its entries don’t appear for you, and the total under the list doesn’t count them. The same goes for a whole area your role can’t open: if your role has no access to the inbox, Files or task lists, you don’t see entries about emails, filed documents, folders, transmittals or task lists. The Audit history panel on an item’s page works the same way. Entries about something that has since been deleted are shown to workspace admins only. So are entries about a connected Slack channel, GitHub repository or ClickUp Space turning private or public, and about the GitHub issues and ClickUp tasks that were restricted because of it. And so are the entries left by the one-off clean-up that took a person’s job title or company off their record, when only restricted sources (a private channel, a sealed bid) had said it: they name those sources.

A task in the Bin is different. While a task is in the Bin, the log shows nothing about it, its replies or its files to anyone, with two exceptions that only workspace admins see: the entry saying who deleted it and when, and, if it was put back once and deleted again, the entry saying who put it back. An entry about something else that mentions the task is shown without its details. Once the task is put back, its entries come back for everyone who can open it.

Some entries also mention a second item. For example, when the AI closes a task on its own, the entry quotes the email that showed the task was done. If you can open the first item but not the second, you still see the entry, but its details and reason are left out. Search doesn’t look inside details that are left out.

A few entries keep something the item’s own page no longer shows: a task reply that was deleted or reworded, or a file taken off a task. You see that the change happened, but not the words or the file name. Once a file is taken off a task, the other entries that name it (the file being added, downloaded, or a reply pinned to it) stop showing their details too. And once a reply is deleted, the entry for posting it stops showing its details: the companies it asked, the questions it answered, and the file it was pinned to.

When someone changes something through chat, the entry’s reason is their chat message (or the assistant’s summary of it). Only that person sees the reason. Everyone else who can open the item still sees the entry and the change itself.

The details of a task list import (the file name, its column headings and any note from the company that sent it) are shown only to the people who review imported lists: someone who can edit tasks and who is either a project lead or works for the company that manages the task list. You also see the details of an import you ran yourself. Undoing an import works the same way: its details (the file name and how many tasks it took out) are shown to those reviewers, and to the person who undid it.

Workspace admins see every entry in full, except entries about a task in the Bin (above).

What’s recorded

Each entry captures one change to one thing (an “entity”), with an action:

• created — a new register entry, stakeholder, email, evidence link, or the project itself
• updated — an existing item was edited
• deleted — an item was removed
• merged / auto_merged — two duplicate items were combined (see the Glossary)

Every entry shows the action, the kind of item, who made the change, a timestamp, and a shortened id for the item.

Who made the change — the three actor kinds

Every entry is attributed to one of three actors. In ddx PMO the AI is a first-class actor, recorded the same way a person is:

Actor	Meaning
user	A signed-in person. The entry shows their email.
llm	The AI (Claude). Shown when classification creates an item or links evidence. The label includes the model.
system	Background processing with no person behind it — for example an inbound email arriving from a source, or a scheduled job.

Note

When you correct something through chat, the entry is attributed to you, with the channel noted (shown as “(via chat)”) and your instruction kept as the reason — shown as a quote on the entry, to you and to workspace admins.

Filtering

Two filters narrow the feed:

• Entity — limit to one kind of item (risk, issue, decision, action item, stakeholder, email, and so on).
• Actor — limit to user, llm, or system changes.

The feed shows the most recent changes first. To trace one item’s full history, the same records appear in the Audit history panel on that item’s detail page.

---

Resetting or deleting a project removes its audit log along with the rest of its data.