Activity log: what is recorded and who can see it
Guide to the Active Logs screen of the company panel: which changes are recorded automatically, who can open it, how to read an entry and what the screen does not show.
Last updated 22 October 2026 · Last verified 22 October 2026
Purpose#
This guide explains the Active Logs screen: which changes the platform records automatically, who in your company can open it, how to read an entry and what it cannot tell you. There is no separate "activity report": this screen is the activity log.
Who can access it#
- Company staff, on the company's own domain, whose role includes the permission
log_read(permission group "logs"). Open Active Logs from the sidebar. A user without the permission does not see the sidebar item, and one who tries to open the page is sent back to the home page. - Company panel only. The screen belongs to the company panel; the platform's central administration panel has no activity-log screen.
- Who has the permission. It is granted through roles. The default Admin and User roles include it; for a company created by the super admin, the first admin's permissions come from the modules of the company plan, and the
logsmodule carrieslog_read. - Scope. The list shows only the entries made by users of your own company. A change made without a signed-in user has no author and is never listed.
What is recorded#
The platform uses an activity-log package. Every model that carries the logging trait is recorded when it is created, updated or deleted, with the signed-in user as the author. Only the fields chosen for that model are stored: the new values for a creation, the new and the old values for an update, and only the old values for a deletion.
| Log name | Fields kept (examples) |
|---|---|
| User | name, email |
| Role | name, permissions |
| Hub | name, phone, address |
| Merchant | user name, business name, current balance |
| MerchantShops | business name, shop name, contact number, address |
| DeliveryMan | user name, current balance |
| parcel | pickup address and phone, customer name, phone and address, invoice number, cash collection, selling price, delivery charge, total delivery amount, current payable |
| General Settings | phone, name, tracking_id, details, prefix |
| Support | user, department, service, priority, subject, description, date |
Other models are recorded in the same way, including delivery charges, packaging, news offers, the fraud list, income and expense records, fund transfers and accounts, merchant and hub payments, and salaries.
Not recorded here. Wallet ledger movements, wallet top-up and withdrawal requests, the status of a parcel and its steps (see the parcel history), sign-ins, and any change made without a signed-in user, such as scheduled jobs and console commands. Saving a parcel after a status change can still add an Updated entry for the parcel, but a parcel entry holds only the fields listed in the table above, and the status is not one of them, so the entry does not show the new status.
Reading the log#
Open Active Logs
Open Active Logs from the sidebar. The list shows the newest entries first, 10 per page.
Read the row
The columns are #, Log Name (the model, for example Hub or parcel), Event (Created or Updated), Subject Type (the full class name of the item that changed), Description and View, which holds the eye button.
Open the details
Press the eye button. A window titled Log Details lists each field with its New and Old value. For a creation the old column is empty; for a deletion only the old values are shown. Field names come from the activity-log language file; a field without a translation appears as
ActivityLogs.<field>.Move between pages
Use the page links under the table. The counter in the # column restarts at 1 on every page; it is not the entry number.
Expected result. You can see what was changed on a record and from which value to which value, but not by whom or when (see below).
What the screen does not show#
- There is no search, filter, date range, export or delete. You can only page through the list.
- The list and the details window show no user and no date: you cannot tell who made a change or when.
- Deletion entries have no translation for their event and description: the cell shows the raw text
levels.deleted. Only Created and Updated have translations. - In the Arabic interface the last column header reads «رأي» (opinion), a mistranslation of View, and the created and updated events read «مخلوق» and «محدث».
Keeping entries#
- Old entries are not deleted automatically: the package's clean-up command (365 days by default) is not scheduled by the platform and the screen has no delete button, so entries stay until the command is run by hand on the server.
- The list is read-only: no screen edits or removes entries.
Common mistakes#
- Looking for the log outside the company panel. Open it on the company domain, with a company staff account, from Active Logs in the sidebar.
- Expecting to learn who changed something. The screen does not show it.
- Expecting wallet movements or the status of a parcel. A parcel entry never shows the status; use the parcel history and the wallet and finance screens instead.
- Expecting changes made by scheduled jobs or console commands. They have no signed-in user and are not listed.
Limits and permissions#
- Staff of a company without an active subscription are redirected to the company plans page before they reach the screen.