Monitoring Administrator Actions in OpenCart

AdminMonitor is an OpenCart module that accurately records administrator actions in the control panel: who did what, and when. If you have multiple employees working on a store, you quickly stop guessing "who deleted a coupon" or "why the settings changed"—instead, you open the log and see the facts.

Purpose of the module

AdminMonitor's primary goal is to provide you with transparency and control over changes in the admin panel. The module intercepts OpenCart system events (before and after actions), generates user-friendly messages, and stores them in a separate database table. This gives you a unified activity log that's easy to filter and clean.

Important: The event log is especially useful when multiple managers, content editors, or external contractors have access to the admin panel. It's a simple "insurance" against errors and disputes.

What exactly is being tracked?

The module registers the action type and entity group being accessed. Built-in event types:

• add - creation
• edit - change
• delete - deletion
• approve - approval
• login - login to the admin panel
• logout - log out of the admin panel

Here are examples of groups (admin sections) for which a log is kept:

• products, categories, manufacturers, options, attributes and attribute groups
• coupons and marketing campaigns
• clients and client groups
• banners, layouts, information pages
• downloads, recurring profiles, filters
• partners and partner transactions
• store settings (including separate processing of the setting/setting section)
• Orders (create/edit/delete - logged on the catalog side to catch actions occurring through API/scripts)

What data is saved in the log?

Each log entry is a structured event. A table called adminmonitor is created in the database, which records the following:

• User ID (user_id) and login (user_name)
• event type (event_type) and group (event_group)
• hook/trigger (argument_hook) - helps to understand the source of the event
• data - most often this is the entity ID (for example, product_id, category_id, order_id)
• subject - a "human" description of the object, often in the form of a link to the editing page
• date and time (date_created)

Interface and working with events

In the admin panel, the module displays a table of events and provides tools for quick checks. The following operations are available:

• filter by user, type, group and date range
• pagination
• bulk delete selected records
• "Clear filters" button to return to the full list
• The "Rehook Events" button - if you need to re-install hooks (rehook)

Benefits of AdminMonitor

• Organize your admin panel you see the change history, not guesswork.
• Quick investigation who removed the banner, who changed the coupon, who edited the product card.
• Team control convenient for distributed employees and agencies.
• Clear messages The log contains readable phrases and clickable links to the object (when possible).
• Order logging support separate handlers for checkout/order events, including add/edit/delete.

Practical application scenarios

1. After a drop in conversion, check if anyone has changed prices, coupons, or store settings.
2. If there is an edit conflict, quickly find out who edited a product/category and when.
3. When working with a contractor, monitor changes without constant “calls and reports.”
4. When cleaning the admin panel, monitor for mass deletions and approvals.

Recommendations for use

To make the journal as useful as possible:

• Provide access to the admin panel individually, do not use one shared account for everyone;
• periodically clear old events (the module has an option to delete selected records);
• After moving your site or updating it, if necessary, click Reconnect Events to ensure all hooks are active.

AdminMonitor is that module that works quietly in the background, but saves hours of time, nerves, and money when you need to quickly restore a picture of what's happening in the admin panel.