Vai al contenuto

Who touched what: the admin activity log

Since 25.7 Maho records backend actions and sign ins with user and IP address: how to read the log and how to tune it.

When a product changes price and nobody says so, or an order disappears, the question is not “what happened” but “who did it”. Without a log the answer comes from a backup and from whoever was in the office that day. Since 25.7 Maho writes a backend activity log, and the answer is a grid with date, user, IP address and page.

What gets recorded

The module has two grids, under System > Admin Activity Log:

  • Activity Log: the list of actions, with user, IP address, request URL and request count;
  • Login Activity: successful and failed sign ins, with the reason for the failure.

The tracked actions are chosen one at a time, because the useful log is the tuned one, not the one that writes everything. The switches live in System > Configuration > Advanced > Admin > Admin Activity Log.

Setting What it records
Enable Admin Activity Log turns the module on
Log Page Visits pages opened
Log Save Actions saves
Log Delete Actions deletions
Log Mass Actions bulk actions
Log Login/Logout Activity sign ins and sign outs
Log Failed Login Attempts failed sign in attempts
Days to Keep Logs days the log is kept, 0 means forever

🕵️ Note in the ledger: “Log Page Visits” is the first one worth leaving off. On a backend used all day it fills the table with noise, and noise is where the useful detail hides.

A sensible configuration

On a store with two or three people in the backend: saves, deletions, bulk actions, sign ins and failed attempts on; page visits off; retention at ninety days. The log then covers the quarter and the table stays readable.

On a backend with more people or with external contributors, page visits become useful again, but raise the retention and read the grid by user rather than by date.

🕵️ Note in the ledger: 0 in the retention setting does not mean “never clean up on purpose”, it means the table only grows. That is a choice, and like every choice it should be made knowing the cost.

What a row tells you

An Activity Log row answers four questions at once: when, who, from where and what. The request count on the same page also tells how many times the same thing was saved within the same minute, which is the fastest way to tell a double click from a deliberate action.

The Login Activity grid adds the failure reason. A user with ten failed attempts in a minute has a password problem; a user with ten failed attempts from ten different addresses has a security problem.

🕵️ Note in the ledger: the log tells you who pressed Save, not who decided to change the price. For that, the conversation remains the only record, and no module keeps it.

Where it actually earns its keep

The log pays off in three concrete moments.

  1. After a content mistake: you see who saved what and when, and compare it with the version history.
  2. After a suspicious sign in: Login Activity shows whether the attempt came from an address nobody on the team owns.
  3. Before removing permissions: reading what a role actually did shows what the person using it really needed.

In those moments the difference is not the amount of data, it is the ability to search. Filter by user and by date range before widening the view, otherwise the list becomes the place where hours disappear.

Text prepared with the help of AI and checked against the source before publication. It can still contain mistakes: if you find one, report it.Read the manifesto

Does your store still sell?

Tell us where you are starting from: we reply with a first assessment, no strings attached.

Ask for the store assessment