Payload Sentinel logs user create, update and delete operations into a centralized audit log collection so you can see who did what and when. It is added through the plugins array and works without configuration. Read-operation logging can be enabled through options, and it integrates with Payload versioning for diff viewing.
Payload Sentinel is a lightweight, opinionated audit logger for Payload CMS.
Installation
npm i payload-sentinel10
Stars
2
Forks
3
Open Issues
1 weeks ago
Last Updated
0
Weekly Downloads
v0.2.2
npm Version
470.1 KB
Unpacked Size
0
Dependencies
Trends appear after 7 days of data. Daily snapshots have not started yet.
Trends appear after 7 days of data. Daily snapshots have not started yet.
Each point is npm's rolling 7-day download count.
Health Score
Composite score based on GitHub activity, stars, npm downloads, publish recency, dependency count, and package size.
Badge for your README
[](https://payloaddirectory.dev/plugins/969401869-root)<a href="https://payloaddirectory.dev/plugins/969401869-root"><img src="https://payloaddirectory.dev/badge/969401869-root.svg" alt="Payload Directory"></a>README
Payload Sentinel is a simple audit logger for Payload CMS. It automatically logs user CRUD operations in a centralized audit log collection, allowing you to track who did what and when.
It:
Requires Payload CMS v3.81.0 or above.
Using npm:
npm install payload-sentinel
Using pnpm:
pnpm add payload-sentinel
Then add the plugin to your payload.config.ts:
import { payloadSentinel } from "payload-sentinel";
export default buildConfig({
plugins: [
payloadSentinel(),
],
});
You're good to go! Payload Sentinel will automatically start logging all user create, update, and delete operations. To enable logging for read operations, see Configuration.
[!TIP] To enable diff viewing in audit logs, make sure versioning is enabled for the relevant collections or globals. Sentinel doesn’t handle diffs itself, nor is it planned to, because Payload already provides built-in versioning, which Sentinel natively integrates with.
Note: Versioning is optional; audit logging still works without it. You just won't be able to view diffs.
Payload Sentinel works without any configuration. If you want to customize its behavior, there are minimal configuration options, which you can check here: config.ts. If there is a feature not currently configurable that you would like to see configurable, you may submit a feature request here.
Please report issues and request features by opening a GitHub issue. PRs are welcome; see CONTRIBUTING.md.
Tags
payload audit
Automatic audit logging of create, update, delete and auth events across all Payload collections
70712/wk4v3
activity log
Log activity on selected collections and globals in a dedicated activity log collection
660/wk114v3
authors info
Tracks who created, edited and published documents across collections and globals
6557/wk181v3
payload auditor
Audit logging for Payload collections and globals using hook operations, with buffered writes and automatic log cleanup
640/wk79v3
activity log
Chronological activity feed of document changes and user logins across all collections and globals
6129/wk15v3
payload hooks
Collection hook helper that logs Payload operations through the Nexload logger
550/wk2v?