Login and logout
See successful login and logout events. Failed attempts live in the separate login-protection history.
When did someone last log in? Was a plugin activated? Did the active theme change? Bearmor records a focused set of security-relevant WordPress events.
The local log covers login and logout, selected plugin lifecycle events, theme switching, user creation and deletion, and Bearmor actions. Each row includes a timestamp and, where available, a username and IP. The table keeps up to 250 records.
See successful login and logout events. Failed attempts live in the separate login-protection history.
Plugin activation and deactivation events recorded by the current plugin.
See when the active theme changes.
User creation and deletion are recorded. General role changes are not claimed.
Rows include a timestamp and an IP where that event provides one.
The log is stored on the WordPress site and capped at 250 records.
A focused event history helps after an unexpected login, plugin change or theme switch. It is not a complete record of every admin click, content edit, file change or settings change.
You can place a recorded login next to other security events.
Activation and deactivation are visible when a plugin change matters.
New and deleted users leave a record.
An unexpected change to the active theme is easier to spot.
The activity log is a compact local history, not a compliance archive and not a full WordPress audit suite. It gives you useful context without claiming events the plugin does not record.
Stored on your site. No export or geographic enrichment is claimed.
Install the free plugin from WordPress.org. Every feature is free, with no paid plan to unlock.
Tell us the site and what you need. A person replies within one business day.
Loading…