Change log
The activity log records every creation, change or deletion of important data: who acted, when, on which object and from which workstation (IP / MAC). It is the central register of internal traceability.
Overview
The Change log (also called the activity log) is generated automatically by Swifto. Every time a user saves a creation, changes a record or deletes one, a trace line is added — with no action required from the user. Nothing is created here manually: the log is only used to view the history for audit, internal control and dispute resolution.
Business goal
- Know who touched a record
- Know when (date & time)
- Identify the workstation of origin (IP / MAC)
- Reconstruct the history of a record
Target audience
- Administrators — oversee activity
- Management / control — internal audit
- Accounting — control of sensitive data
One log among others
This log is part of the Logs module. It is complemented by the Connection log (who was logged in at the time of the action) and the Business logs (prices, invoices, terminals…).
Access and navigation
Left-hand side menu: Logs → Change log. It is one of the three logs always available (along with System connections and Sales log), subject to profile rights.
Visibility conditioned by profile
Reading the activity log is generally reserved for the Manager and Administrator profiles. If the entry does not appear in your menu, your profile does not allow you to view it.
List of changes
The page displays the list of events, from most recent to oldest. Each row describes a single operation with its author, its type, the object touched and the technical origin.
| Date⇅ | User⇅ | Type⇅ | Class⇅ | Element | IP address | MAC address | |
|---|---|---|---|---|---|---|---|
| 04/06/2026 14:32 | Mouadh BEN AZIZA | Edit | Item | 467802 - SMART MODULE | 192.168.1.24 | A4:5E:60:C1:0F:7B | |
| 04/06/2026 11:08 | Salma TRABELSI | Creation | Customer | EL MAZRAA | 192.168.1.31 | D8:9E:F3:22:1A:55 | |
| 03/06/2026 16:45 | Ayatollah ORABI | Deletion | Price list | June promo grid | 102.107.135.198 | C0:3F:D5:88:9E:01 | |
| 03/06/2026 09:21 | Sami GHARBI | Edit | Invoice | SY000323 | 192.168.1.18 | 8C:16:45:2A:B7:E0 |
Each column has a quick filter and a sort (⇅ arrows). Click the header to sort, for example by User to group all the actions of the same person.
Columns & detail
Table columns
| Column | Description |
|---|---|
| Change date | Exact date and time of the operation. |
| User | First and last name of the author of the action. |
| Change type | Creation, change or deletion (section 5). |
| Class | Type of object concerned (Item, Customer, Invoice, Price list…). |
| Selected element | The precise record that was touched (reference or label). |
| IP address | Network address of the workstation behind the action. |
| MAC address | Hardware identifier of the terminal (if available). |
IP & MAC: linking the action to a workstation
The IP and the MAC make it possible to identify the physical workstation an operation came from — valuable in the event of a dispute or suspected unauthorized access. The MAC can be empty when the action comes from a channel that does not transmit it.
Operation types
| Type | Meaning | Example |
|---|---|---|
| Creation | A new record is added. | New customer "EL MAZRAA". |
| Change | An existing record is updated. | Price of an item changed. |
| Deletion | A record is deleted. | Price list removed. |
To reconstruct the life of a record, filter on the Class and Element concerned: you get its full timeline (creation → successive changes → possible deletion).
Filters & search
The Search button opens a filtering window by period, user and operation type. The quick per-column filters remain available in the table header.
Advanced search
On large volumes, narrow the period first: the display is faster and the export lighter.
Export
The filtered list can be exported for archiving or transmission to an auditor.
PDF export
Printable document of the filtered log, in the chosen language ("PDF English" menu).
Excel export
Rows exported to a spreadsheet for analysis (sorting, pivot tables, cross-checks).
The export reflects the current filter. Apply the right period before exporting, otherwise the file will contain all visible rows.
Rules, roles & permissions
Immutability — the log is read-only: no row can be edited or deleted from the interface. This is the condition for its evidentiary value.
Automatic recording — the trace is created by the system at the moment of the action; the user has nothing to do for it to exist.
Company-level partitioning — you only see the changes in your company; data from other accounts remains invisible.
Permission matrix
| Action | Operator | Accountant | Manager | Admin |
|---|---|---|---|---|
| View the change log | — | — | ✅ | ✅ |
| Filter / search | — | — | ✅ | ✅ |
| Export (PDF / Excel) | — | — | ✅ | ✅ |
| Edit / delete a row | — | — | — | — |
Indicative matrix — actual visibility depends on the profile privileges and the options enabled for your company.
Audit scenarios
A price list has disappeared
The "June promo grid" no longer exists. Filter Class = Price list: the log shows a Deletion on 03/06 by Ayatollah ORABI from IP 102.107.135.198. The author and the workstation are established.
Cross-checking with connections
To confirm the author of a questionable action, cross-check the time and IP of the row with the Connection log: who had a session open on that workstation at that moment?
FAQ & Tips
I don't see the log in my menu?
Viewing it is reserved for Manager / Admin profiles. Ask your administrator for the corresponding privilege.
Can I correct an erroneous row?
No. A trace reflects a real action and cannot be modified. Correct the source data in its own module: this will create a new row in the change log.
Why is the MAC address sometimes empty?
Some channels do not transmit the MAC (network, browser, device type). The IP, on the other hand, is almost always available.
Best practice — monthly audit
Every month, export the log filtered on the period and archive it. You will have an enforceable history even in the event of a purge.
