Admin and developer tools
Admin Activity Log
See who changed what in the Magento admin, with old and new values, plus every admin sign-in, the active sessions and alerts for suspicious sign-ins.
We use necessary cookies to make this site work. With your permission we also use Google Analytics to understand how the site is used and Google Ads cookies to measure which of our ads lead to purchases. You can accept all cookies, reject the optional ones or choose which ones to allow. Cookie policy
Choose which cookies you allow. Necessary cookies are always on because the shop cannot work without them. You can change your choice at any time with the "Cookie settings" link.
Needed for the basket, checkout, login and security. They do not track you.
Google Analytics: how many people visit, which pages they read and how they found the site. It sets the _ga cookies and sends usage data to Google.
Google Ads: measures which of our ads lead to a purchase. It sets the cookies _gcl_au and _gcl_aw (90 days) and, when you buy, sends Google the order details and a hashed form of your contact details for matching. See our cookie and privacy policies.
Admin and developer tools
See who changed what in the Magento admin, with old and new values, plus every admin sign-in, the active sessions and alerts for suspicious sign-ins.
Admin and developer tools
See, run and control every Magento cron job from the admin, and get warned when cron stops or a job keeps failing.
Tools for the people who run a Magento 2 store day to day: see and control cron jobs, and see who changed what in the admin with a Magento 2 admin log.
Magento relies on cron for emails, indexes, price rules and much more, but has no admin screen to see or control it. Cron Manager lists every cron job with its schedule, last run, status and average duration. You can run a job now, enable or disable it and change its schedule without editing code, see the cron_schedule table as a grid and as a timeline, and clean up the queue. It warns you when cron stops running or a job keeps failing, and can send failure emails.
Our posts explain how to tell when cron has stopped and how to pause or reschedule one cron job.
Magento Open Source records when a product was last updated, but not who changed it or what the old value was. Admin Activity Log keeps an admin action log with old and new values field by field for products, categories, CMS pages, customers, orders, price rules, configuration, admin users and roles. Mass actions, imports and config:set from the command line are logged too.
The login history shows successful and failed sign-ins, the active sessions list shows who is signed in now and lets you end a session, and you can get security notifications and limit the admin to an IP allowlist. Passwords, keys and other secrets are masked in the log. See who changed this price?
Cron Manager works with Magento's own cron, so the server crontab still has to be set up; the module shows you when it is not running. The activity log records changes made in the admin and through config:set, so changes made straight in the database are outside its view.
Yes. Cron Manager can disable one job or give it a new schedule from the admin. The change is stored in the configuration, so it can be exported with app:config:dump, and the job can still be run by hand.
No. Passwords, tokens, keys and other sensitive configuration values are stored masked. You can still see that they were changed and by whom.
Yes. Magento's cron still has to run from the server crontab. Cron Manager shows and controls the jobs and warns you when cron has stopped.
From the blog
Sharing Magento roots helps. It does not replace checking the package constraints, edition-specific code and workflows your business depends on.
‘We updated Magento’ is a useful start. In 2026, you also need to know which isolated patches and component fixes actually reached production.
The old Magento user guide links now land on Adobe's documentation site. Where the manual is, how to keep a copy, and how to spot the pages that describe features your Open Source store does not have.
When you delete a product, Magento removes its URLs and the page becomes a 404. That is sometimes right and often a waste. Here is how to decide, and how to stop it happening by accident.
Magento can send through an SMTP server since 2.4.6, but it cannot tell you which emails failed or sign in to Microsoft 365 with OAuth. Here is how to set up SMTP properly and keep an eye on it.
Packing from the Magento order grid means opening one order after another to see what is in it. Here is what the grid can show on its own, what it cannot, and a free way to add the missing columns.