Overview
The audit log records every action in Polygon One without gaps — whether performed by a team member, a supplier through the portal, or a system automation. This lets administrators trace at any time who made which change and when, and to which record. You’ll find the audit log under Settings → Administration → Audit log. The view is read-only and only visible to company administrators. Entries can neither be edited nor deleted. The list shows the entries of the currently active module: in the EUDR module you see the EUDR and the cross-module entries, in the PPWR module the packaging and the cross-module ones. Switch the module and the excerpt switches with it.Columns
The Action, Entity and Details columns can be hidden through the column picker; Time and Actor cannot — without them an entry could not be read.
Four kinds of actor
Searching and Filtering
- Search — the box above the table (“Search actions…”) matches the technical action name (English, e.g. deleted or created), not the label shown in the table and not the actors, entities or details. To narrow to one operation, use the Action filter — it offers the displayed names
- Actor — restrict to individual team members
- Actor type — Member, Supplier, Integration or System
- Entity type — see the list under Logged Actions
- Action — restrict to individual operations
- Date range — select a from/to date
Detail View
Click an entry to open the “Audit entry” dialog. It shows the time, actor, entity and Entity ID, then a Changes table with Field, Before and After, plus the remaining logged Details in a readable form. When there is nothing further to show, it reads “No additional details”.Logged Actions
It is not only the EUDR part of the platform that is logged. The Entity type filter offers these kinds of record — which of them depends on the active module:
Depending on the kind of record, creation, update, import, deletion and restoration are captured — which of them depends on which operations exist for that kind at all. On top of that come the domain events — such as DDS submitted, EUDR status overridden or Supplier assigned — the linking of input articles, and the data suppliers submit through the portal (compliance data, geodata, documents).
The end of the retention period is logged too. When the automatic retention cleanup removes a record for good, it writes its own ”… permanently deleted” entry with System as the actor — one per top-level record removed (article, supplier, plot, document, DDS statement, packaging unit …). Dependent records that go with it get no entry of their own. The proof that something was deleted thus outlives the deleted record.
If an entry refers to a record that has since been deleted or belongs to another company, a neutral note is shown instead of a link. This keeps other tenants’ data protected.
Handing evidence to an authority: the audit package
The audit log itself has no export button — it is the research view inside the application. When you have to hand evidence to an authority, an auditor or a customer, use the audit package instead. The audit package bundles everything collected for one supplier into a ZIP archive: the data and analysis results for that supplier and its articles as CSV files, the files that belong to them in their original form, and a manifest file with the time of creation, the scope and the row and file counts. The files it contains are the uploaded evidence and legal documents, the generated report PDFs, the submission snapshots of the DDS statements, the plot map images and the attachments from the correspondence with that supplier. If packaging data has been recorded for its articles, the corresponding packaging evidence is included as well.1
Open the supplier
In Inbound, go to the supplier you need evidence for and open its action menu. The package can be created by the Owner, Admin and Editor roles, provided the EUDR module is enabled for them; a Reader cannot.
2
Download the audit package
Choose Download audit package.
3
Wait for the assembly
The package is assembled in the background (“Assembling audit package…”). With many documents this takes a moment; you can keep working. Once it is ready, “Audit package ready” appears and the download starts by itself. If an assembly for the same supplier is already running, no second one is started — the app tells you so and attaches to the running one, so the download still arrives.
If the assembly takes unusually long, the app tells you so and stops waiting — simply start it again later. The contents always reflect your data at the moment the package was assembled.