Audit Log
unlistedby Remy Honig
Track file movements and log them inside each file.
Updated 3mo ago0BSD
Audit Log
Track where your notes have been. When you move a file, an entry is added inside that file so you can look back and see its journey through your vault.
Why use this?
- Folder-based task management: If you organize projects or tasks by moving them between folders (like
Backlog,In Progress,Done), each move becomes a logged state change. At review time, query all state transitions to see what moved forward, what got stuck, and what finished—without maintaining a separate tracking system. - Remember context: See where a note came from when you revisit it months later
- Query with Dataview: Find all notes that passed through a specific folder, or see movements across your vault in any time period
How it works
- Configure which folders to watch in settings
- Move a file into, out of, or within a watched folder
- The plugin adds a log entry inside the file under a heading (default:
## Audit Log)
Log entries look like this:
## Audit Log
- [moved:: 2025-12-21T10:30:00] [src:: `Inbox`] [dst:: `Projects/Active`]
- [moved:: 2025-12-22T14:15:00] [src:: `Projects/Active`] [dst:: `Archive`]
The format uses Dataview inline fields, so you can query your file history:
TABLE moved, src, dst
FROM "Projects"
WHERE moved
SORT moved DESC
Settings
Each watched directory can be configured independently:
- Directory path: Which folder to monitor (includes subfolders)
- Audit log heading: Where to add entries in your files
- Create heading if missing: Automatically add the heading to files that don't have it
- Use full path: Show complete paths or just the relative portion
- Debounce time: Avoid cluttering the log when reorganizing—multiple moves within this window update the same entry
Installation
From Obsidian
- Open Settings → Community plugins
- Search for "Audit Log"
- Install and enable
Manual
- Download the latest release from GitHub
- Extract to
<vault>/.obsidian/plugins/obsidian-audit-log/ - Reload Obsidian and enable in Settings → Community plugins
Support
Found a bug or have a suggestion? Open an issue on GitHub.
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.