DIJJI.ai keeps a record of the changes made to your work. Whenever something is created, edited, removed, or moves through a run, an entry goes into an audit log. This page explains where to find it, what an entry tells you, and who can see it.
Where the audit log lives
There is no single, site-wide activity feed. Instead, each thing in DIJJI.ai carries its own audit log, shown as a collapsible Audit Log panel on that thing’s detail page.
You’ll find an Audit Log panel on the detail page of:
- An organization — under Settings → Organization.
- A team — under Settings → Team.
- A member — under Settings → Members.
- A project — on the project’s overview page.
- A task — on the task’s detail page.
- An integration — on the integration’s detail page.
The panel starts collapsed. Click the Audit Log header (with the ▸ arrow) to open it; the entries load the first time you expand it. Each panel shows only the history of the thing you’re looking at — open a project’s panel and you see that project’s changes, open a member’s panel and you see that person’s.
What an entry looks like
Entries are listed newest first. A single entry has three parts:
- The action — a short word for what happened, shown in bold. For example
created,updated,triggered,completed,invited. - Who did it — shown as by followed by the person who made the change, or by system when DIJJI.ai made the change automatically (for example, charging credits at the end of a run).
- When — the full date and time, shown on the right, in your browser’s local time zone.
If the action changed specific fields, the entry expands to list them underneath, one per line, in the form field: old value → new value. The old value is struck through. An empty value shows as ∅. So renaming a project from “Billing” to “Payments” reads:
updated by Dana Okafor 5/22/2026, 2:43:15 PM
name: Billing → Payments
Some entries carry extra detail instead of field changes — an invitation entry, for instance, lists the email address it was sent to. These appear the same way, as a short list below the action.
What gets recorded
The audit log captures the meaningful changes to each thing, not every click. Across the product you’ll see actions such as:
- created, updated, deleted — something was made, edited, or removed.
- triggered, cancelled, completed, failed, resumed — a run started, was stopped, finished, fell over, or picked back up.
- invited, joined, removed — a person was invited to the organization or a team, accepted, or was taken off.
- connected, disconnected — an integration was linked or unlinked.
- top_up, charged, refunded — a billing event: credits added, spent, or returned.
If a panel has nothing to show, it reads “No audit entries — No mutations have been recorded for this record yet.” That’s normal for something brand new.
Reading a long history
Each panel shows 20 entries at a time. When there are more, paging controls appear at the bottom of the panel so you can step back through older entries. There’s no search, filter, or date-range picker — the log is a straight reverse-chronological list, so the most recent change is always at the top.
Who can see it
The Audit Log panel is admin-only. If you’re an admin, you’ll see the panel on every detail page listed above. If you’re a member, the panel doesn’t appear at all — there’s no greyed-out version, it’s simply not rendered.
This is why audit history is in the admin column on the Roles page: reviewing who changed what is part of running the organization, not part of the everyday delivery work.
In short: every organization, team, member, project, task, and integration keeps its own Audit Log — a newest-first record of what changed, who changed it, and when. Expand the panel on a detail page to read it. Only admins can see it.