Logged.ai – Activity Log & Audit Trail

By Plugins.shop

0+ active installationsVersion 1.2.15

WordPress activity log for user, content and WooCommerce changes. Review your audit trail and export CSV or JSON, with no account required.

Description

Know who changed what on your WordPress site. Logged.ai gives you a local activity log for supported user actions, content edits, settings and WooCommerce changes, so you can investigate a problem with recorded context.

Find a change, inspect its details and open the affected item with your current permissions. History stays in your WordPress database. Free needs no vendor account, subscription or external AI service.

Try the Free and Pro demos

Real plugin screens, fictional records, no account needed. Explore screens and filters; permanent saves, message delivery and response enforcement are disabled. The Pro demo shows the separate paid add-on.

Setup guides | Reference | Support

What you can do with Free

  • Review user activity. Inspect supported logins, logouts, account and role changes. Distinguish the acting and affected users without storing passwords or sensitive profile values.
  • Investigate content and settings changes. Filter activity, open accessible items and follow retained revisions. Identify supported setting changes, including site title and tagline, without retaining their text. Current content titles stay separate from historical evidence.
  • Review WooCommerce activity. Inspect supported price, stock and order changes and stored refund facts, with recorded currencies and explicit missing values. WooCommerce is optional.
  • Open an item’s history. Use shortcuts in supported content, product and order editors, including HPOS, without saving or leaving your work.
  • Export your evidence. Download spreadsheet-friendly CSV or structured JSON. Request observations and retained context have a separate JSON export.
  • Inspect request findings. Filter WordPress-layer observations. Preview and confirm temporary manual response policies, with expiry and recovery.
  • Control privacy and retention. Configure collection and retention, use scoped views and exports, and keep critical security and failure notices in Free.

Essentials, Operator and Expert change display detail, not collection or permissions. Local Pro previews can be hidden for your administrator account.

When the Pro add-on helps

Add Pro for recurring team reviews; keep Free installed.

  • Scheduled reports: reuse saved searches and schedule private reports.
  • Advanced alerts: configure rules and notify your team through email, Slack or webhooks. Routine activity notification emails are a Pro feature; critical security and failure notices remain Free.
  • Cases & handover: keep related evidence, notes, assignments and decisions together.

Pro requires a compatible Free installation and first licence activation. Opening a preview or tool does not enable alerts, schedules or response policies. Destinations and sending require configuration. Compare features and explore Pro.

Coverage you can understand

Supported hooks are recorded, not every database write. Direct SQL, unsupported integrations and activity while disabled can be missing. Raw content and sensitive values are excluded.

Request findings are observations, not proof of an attack. The sensor cannot see all cached, static or upstream traffic. A local response is distinct from an arbitrary HTTP 403. Equivalent PHP/database operators can change local evidence; it is not tamper-proof.

More from Plugins.shop

Optional companions from the same publisher:

These are separate products, not dependencies or automatic integrations. Check their pages for availability and requirements. The local More Plugins page installs nothing and sends no usage data.

The listing screenshots below were captured in Logged.ai Free 1.2.6 using fictional records.

Installation

  1. Install and activate Logged.ai from Plugins > Add New, or upload the Free plugin ZIP.
  2. Open Logged.ai > Setup and review collection, retention and request-address settings.
  3. Make a supported test change and inspect it in Activity. Use the built-in request observation check to understand the sensor’s coverage.
  4. Configure optional notices or response policies only after reviewing their scope and recipients.

Requires WordPress 6.7+, PHP 8.0+ and MySQL or MariaDB through the standard WordPress database adapter. InnoDB is required for protected exports and privacy changes, including the relevant WordPress options table. SQLite and WordPress Playground’s SQLite database are unsupported; Logged.ai opens paused diagnostics rather than creating its tables. It does not convert tables automatically.

Background exports and cleanup need working WordPress scheduling. PHP 8.0/8.1 must allow exception-argument capture to be disabled; otherwise activation/loading pauses with guidance. PHP 8.2+ uses native sensitive-parameter redaction.

Back up your database before updating. Replace plugin files without uninstalling; use matched Free and Pro packages when using the add-on. Details are in docs/technical-reference.txt and the export guide.

FAQ

Does Free need an account or a licence?

No. Free works independently. Routine activity emails, configurable team alerts, scheduled reports and cases require the separate Pro add-on.

Does the .ai name mean my activity is sent to an AI service?

No. Local collection sends no activity data to Logged.ai or an AI service. Local initials replace external profile images. Notices use your WordPress mail service; mail acceptance does not prove delivery. Product links contact external sites only when followed.

What can I download immediately?

Download now creates CSV/JSON in memory: up to 1,000 records and 2 MiB. Oversized selections are refused, never silently truncated. It needs no Sodium, temporary directory or cron, but requires supported database locking and current authorization.

Separate request JSON includes up to 500 observations, 100 groups and 100 policy-history entries, with caps disclosed. It is not a complete traffic log or atomic snapshot. Date filters use UTC. Secure plaintext downloads: local copies cannot be recalled.

How do prepared exports work?

Prepared activity exports use encrypted database chunks and background jobs, require PHP Sodium and working scheduling, and expire after 24 hours. Limits are 1,000,000 rows and 256 MiB, not a performance guarantee. Personal-data export jobs use this saved mechanism. Keep the original WordPress authentication salts to read saved exports.

Does export storage require Unix filesystem permissions?

New saved chunks do not require Unix filesystem permissions; legacy file chunks still need their original compatible storage until cleanup completes. On Windows, automatic legacy file cleanup is unavailable: legacy job records remain pending, and delete-all uninstall retains the tables. Ask your host to verify and complete this cleanup, even if the old folders appear absent. Database-only jobs retain their database cleanup path.

Why does a failed sign-in sometimes have no Activity entry?

Failed sign-ins are grouped. Ten observed failures within the same fixed five-minute interval create a burst entry; fewer failures have no individual Activity entries. Intervals restart every five minutes, so attempts across a boundary are counted separately. Supported native WordPress failures against an existing account can also create a separate account-targeted burst. That identifies the account targeted, not the person attempting to sign in. Passwords and attempted login text are never retained.

Requests contains matching findings, not a complete sign-in or traffic log. An upstream block or unsupported authentication integration may not reach the supported WordPress hooks. If an expected burst is missing, review System status and collection coverage.

What data is retained?

Approved identifiers, change facts and UTC timestamps are stored locally. Administrative collectors exclude passwords, raw content and sensitive profile values. Request addresses default to masked direct peers; full addresses require explicit selection and permissions. Forwarded headers are ignored unless you configure a trusted proxy boundary.

Defaults are 90 days for activity, 7 for minimized requests, 30 for groups/inactive response history and 14 for explicitly selected exact addresses. Cleanup may be delayed by cron; current privacy restrictions still apply to viewing and exports. Personal-data erasure removes associated events and linked addresses.

Can I use it on a multisite network?

Site views are permission-scoped. Network exports need separate authorization. Ordinary site exports and erasure cannot include another site’s evidence.

What happens if I deactivate or uninstall?

Deactivation preserves data. Uninstall also preserves it unless the separately confirmed installation-wide delete option is enabled. That option removes Logged.ai-owned data, settings, jobs and capabilities only after private export cleanup is verified. If legacy export cleanup cannot be verified, uninstall stops and retains the tables. On Windows this automatic verification is unavailable, so delete-all uninstall requires host-assisted verification and cleanup outside the plugin. Previously downloaded files remain outside the plugin’s control.

Does Logged.ai ask for a review?

An optional invitation appears for settings managers on production sites 30 days after their first Overview visit, once they have opened it on three separate UTC dates. You can postpone it for 30 days or dismiss it permanently. Reminder preferences and up to three use dates stay on your site, are shared by Free and Pro, and are covered by personal-data export and erasure. No activity content or satisfaction score is used, and nothing is sent automatically. The sidebar also provides a direct WordPress.org review link.

Screenshots

Changelog

1.2.15

  • Add an optional, neutral WordPress.org review invitation after 30 days and three separate Overview-use dates, with local per-user/site snooze and permanent dismissal.
  • Add a direct WordPress.org review link for settings managers, shared by Free and Pro.

1.2.14

  • Match the Pro alert-validation status and background-consent confirmation improvements. Free collection, stored data and minimum requirements are unchanged.

1.2.13

  • Avoid misleading UTC-offset and pending administrator-email entries from unrelated General Settings saves. Continue recording verified setting changes with private values redacted.
  • Match the Pro alert-scanning and background-consent corrections without changing minimum requirements.

1.2.12

  • Match the Pro 1.2.12 maintenance release, which verifies background-job cleanup during deactivation and safely retries bounded concurrent schedule changes.
  • Preserve Free collection, WooCommerce variation evidence, exports, privacy and access controls.

1.2.11

  • Record newly generated WooCommerce variations when the native data store applies its default published status. Preserve independent stored-value checks and product-text redaction.
  • Match the Pro 1.2.11 maintenance release.

1.2.10

  • Record product creation when WordPress first autosaves a new WooCommerce product as a draft. Later publishing remains a separate change. Product titles and content stay redacted.
  • Match the Pro 1.2.10 maintenance release.

1.2.9

  • Avoid object-permission notices when a custom capability requires an item ID. Unsupported editor shortcuts remain unavailable rather than weakening access checks.
  • Record WooCommerce classic-editor product creation and title-only changes while keeping product text redacted and avoiding duplicate CRUD events.
  • Keep disabled Pro alert rules editable while making unavailable activation-dependent controls clear in the matched add-on.

1.2.8

  • Use neutral content-date labels when WordPress adjusts a draft date during a save. Explain the distinction without changing recorded events or redaction.
  • Match the Pro 1.2.8 maintenance release.

1.2.7

  • Align the Free and Pro release numbers at 1.2.7 so installation and update instructions identify the matching pair.
  • Preserve the verified WordPress 6.7 / PHP 8.0 requirements and existing Free behavior. Update Free first, then Pro without uninstalling.

1.2.6

  • Refresh the Free screenshot gallery with current workflow captures and clearer export guidance.
  • Let the matched Pro add-on recognize verified native plugin-installation events for its configured routine notifications; Free critical notices remain unchanged.
  • Keep password-reset logging verified against stored reset hashes on WordPress 6.7 and newer.
  • Improve native WooCommerce HPOS refund-deletion logging while preserving deletion decisions and transaction ownership.
  • Keep primary action labels readable when hovered or focused, including in the shared Pro workspace.
  • Lower the minimum WordPress requirement to 6.7 while retaining PHP 8.0 and the existing feature and security requirements.

1.2.5

  • Restrict Explore Pro and its local previews to users authorized to manage Logged.ai settings; default Editors and Subscribers cannot open the page.
  • Hide preview invitations and dialogs from users without that permission, while preserving their separately granted workflow access.
  • Apply the same site-scoped authorization to preview preferences.
  • Keep licence notices below the Pro preview page heading so the title stays readable on mobile.

1.2.4

  • Explain the ten-failure, fixed five-minute sign-in grouping in Activity, Requests and the documentation.
  • Harden remaining direct reads of serialized WordPress metadata with bounded, object-free decoding and explicit errors for unsupported data.
  • Check stored uninstall metadata before cleanup, retaining data when safe decoding cannot be established.
  • Preserve normal uninstall retention, the explicit delete choice, existing Windows cleanup limits and current minimum requirements.

1.2.3

  • Stop reporting unverified Windows legacy export cleanup as complete. Retain legacy job records and block delete-all uninstall pending host-assisted verification and cleanup.
  • Process database-only export cleanup before pending Windows legacy jobs so newer encrypted chunks can still be removed.
  • Bound trusted proxy networks to IPv4 /8–/32 and IPv6 /16–/128, including mapped IPv6 input; keep exact addresses and public CDN ranges supported.
  • Reject previously saved overly broad proxy configurations and explain explicit recovery without silently changing settings.
  • Preserve database-only saved exports, Free features, Pro licensing and the existing minimum requirements.

1.2.2

  • Record native site-title and tagline changes with the acting user and time, while keeping setting values redacted.
  • Show readable setting names and distinguish recorded administrator-email requests from confirmed changes.
  • Put export controls first, with visible UTC date guidance and limits and expandable technical details.
  • Fix background case cleanup when WooCommerce registers additional database tables, while preserving privacy and connection checks.
  • Preserve export authorization, private storage, background processing and Pro licensing behavior.

1.2.1

  • Group everyday tools before Setup and Settings, followed by optional Pro discovery.
  • Add compact local Pro previews with a persistent per-administrator show/hide switch.
  • Add a local More Plugins page and Plugins.shop attribution within the plugin workspace.
  • Preserve existing collection, data, permissions, alerts and Pro activation behavior.

1.2.0

  • Establish the revised launch Free/Pro split; retain stored data and existing licence terms.

Earlier history is included in docs/changelog.txt. Website release notes.