The audit trail

For: Staff with the Supporter, Admin or Super Admin role; the Marketplace Editor role for their partnersRequires: The Supporter role or higher; the Marketplace Editor role for one partner user at a timeScreenshots show sample data

The audit trail records every relevant action in comrce Hub and in the connected tools, and nobody can edit it. Support and admins use it to find out what happened in an account and who did it. The Logs show it from six entry points, each already filtered to a company, a person or both.

What it does

Support and admins need to reconstruct what happened in an account without asking the people involved. They also need to tell actions by a customer from actions by comrce staff working on the customer’s behalf.

comrce Hub writes an event for every recorded action. Each event has a timestamp, a source and an event type. It names the account and company it belongs to and holds a JSON payload with the details. It also names the team member acting on the customer’s behalf, if any.

Events cannot be edited or deleted from the console. From there:

Each event has one of 113 filterable event types with a readable label, from sign-ins to Marketplace edits. Event types and their labels.
Six buttons open the Logs pre-filtered to a company, a person or both. The six entry points.
Actions done with a service PIN show which team member did them. Understanding who an event belongs to.
A Marketplace Editor sees one partner’s events at a time. The restricted editor view.

Every payload is shown exactly as stored, so what you read in the Logs is the evidence itself.

Before you start

Requirement	Details
Role	Supporter, Admin or Super Admin for the full Logs. Marketplace Editor for partner users only.
Where	Logs, or View Logs on a company, user or team member page.
Setup	None. Recording is always on, and there is nothing to switch on or configure.
Cost	None.

Understanding who an event belongs to

Every event is recorded under at most one account, the user of the event, and at most one company. Which account that is depends on the action:

Action	Recorded under (User Email)	Company	Who did it
A customer signs in or changes data	The customer	Their current company	The customer
A team member works in a customer’s account with a service PIN	The customer, with a badge showing the team member’s email	The customer’s company	The team member
A team member signs in to the console	The team member	None	The team member
An admin invites someone	The admin	None	The admin
An admin changes a role, resets 2FA or deletes a team member	The person who was changed	None	The admin, named in the payload
An admin edits a company’s details	Nobody (”-”)	The company	The admin, named in the payload
A connected tool reports an event	The user the tool names	The company the tool names	The tool

How comrce Hub decides

The actor switch looks at the event’s user. External keeps events whose user is a customer. Internal keeps those whose user is a hub team account. Events with no user appear only under All.
A Supporter always sees customer events only. For this role the actor switch is hidden, and every Logs tab works as External. Hub team events and events without a user do not appear, and the user filter offers customers only.
Work with a service PIN counts as external, because the event’s user is the customer.
A company filter includes the company’s own events. It also includes the company-less events of anyone who is or was a member, such as sign-ins.
The user filter matches the event’s user. It does not find what someone did with a service PIN, nor role changes they made. The search field does find PIN work, because it also matches the acting team member’s email.

What does not get recorded

Reading pages and lists in the console or the customer area.
Requests that were refused before anything changed, for example a role change outside your authority.
Events a connected tool did not send.

Find out who changed something

A customer asks who removed a colleague, or a setting changed overnight? Three steps take you from the question to the event that answers it. Nothing you do here changes the account.

Start from the person or company. Open the team member, user or company the question is about and select View Logs. A new Logs tab opens, named after them.

View Logs on a team member's page opens their audit trail in its own tab.
What this screenshot shows
Highlighted
“View Logs”: opens the Logs filtered to this team member, scope Internal
Also visible
Delete button next to it
Purpose
one of the six entry points to the audit trail
Narrow down. Add an event type or a source, or widen the date range. The filters you came with stay.

A pre-filtered Logs tab: one person, scope Internal, the last three months, every filter still changeable.
What this screenshot shows
Screen
Logs
Highlighted
“Internal”: keeps the scope on staff accounts
Also visible
User filter: Sophie Wagner (sophie.wagner@example.com); Seven events of her own
Purpose
what a pre-filtered tab contains
Read the payload. Select the payload cell of the row you need for the full details.

Check regularly who on the team can do what

Access tends to grow quietly: a role raised for one project stays long after the project ends. A regular review takes five steps, changes nothing while you look, and every finding links to the person’s page. Run it at least whenever someone changes team.

List the team by role. Open Hub Team and pick each role in the role filter (The team list). Compare each person’s role with Staff roles and what they can do.
List every access change. In Logs, set the actor switch to All. Select the event types User role changed, User 2FA disabled and Internal user deleted. The payload names the admin behind each change.
Check each person’s sign-ins. Open their page and select View Logs. Their tab lists their own sign-ins and console actions.
Find their work in customer accounts. Search their whole email under All. Work with a service PIN is recorded under the customer, so only the search finds it.
Lower a role that is too broad. Change it on the person’s page (Change a colleague’s role when their job changes). comrce Hub saves it once you confirm, and the Logs record it with your name.

The filters of a Logs tab

What you control is the filter state of a Logs tab. Each filter is described as it appears in a pre-filtered tab.

The six entry points

Where

View Logs on five pages, plus the sidebar entry. Each opens its own tab, named after the person or company, for example “Sophie Wagner Logs”.

What

Entry point	Pre-set filters	Who sees the button
Sidebar Logs	None, actor switch on All	Supporter and higher
A company’s page	The company, External	Supporter and higher
A customer user’s page	The user, External	Supporter and higher
A user’s membership in a company	The company and the user, External	Supporter and higher
A team member’s page	The team member, Internal	Admin and higher
A Marketplace partner user’s page	The partner, Internal	Everyone who can open the page

Every tab starts with the date range on the last three months up to today. Every pre-set filter can be changed in the tab, with two exceptions. A Marketplace Editor cannot change any. A Supporter always stays on customer events.

Why

The question usually starts on a page about one customer or one colleague. The button carries that context into the Logs.

Actor switch in a pre-filtered tab

Where

Top right of the Logs tab.

What

Starts on the value of the entry point. Switching it clears the user filter, and Internal also clears the company filter. Hidden for a Supporter and a Marketplace Editor.

Why

A company’s log opens on customer activity. Switching to All adds admin edits of the company, which have no user.

Search for a team member’s PIN work

Where

The search field Search logs.

What

Matches the source, event type, user email and company name. It also matches the email of the team member who acted with a service PIN. Typing the team member’s whole email under All lists everything they did in customer accounts.

Why

Work done with a service PIN is recorded under the customer. The team member’s own tab therefore does not show it.

The Logs screen with "All" selected and sophie.wagner@example.com typed into the highlighted search field "Search logs". The result shows the events Sophie Wagner caused while working in customer accounts with a service PIN: "Updated company info" and "Impersonation by PIN succeeded" for lena.hoffmann@example.com at Nordwind Handels GmbH, and "Edited permissions" and "Impersonation by PIN succeeded" for max.richter@example.com at Elbstrand Living GmbH. Each row shows the customer's email with a badge sophie.wagner@example.com below it. These events do not appear in her pre-filtered tab. — Searching a team member's email also finds what they did inside customer accounts.

Event type filter for access changes

Where

Event Types in the filter row.

What

Lists all filterable event types by label. Select User role changed, User 2FA disabled and Internal user deleted together. That gives a complete list of access changes to the team. The admin who made each one is in the payload.

Why

These events are recorded under the changed person. Only a filter by type lists all of them.

The Logs screen filtered with the Event Types filter, whose button now reads "User role changed" and is highlighted. The table shows three role changes, newest first: tobias.krueger@example.com on 10/03/2026, lukas.hartmann@example.com on 03/03/2026 and katrin.vogel@example.com on 24/02/2026. The User Email column shows the person whose role changed, not the admin who changed it; the admin's email is in the Payload column as "ActingAdminEmail". — Role changes are logged under the person whose role changed. The payload names the admin.

How the settings combine

You want	Actor switch	Filter	Search
Everything a customer did	External	User	–
Everything that happened in a company, including admin edits	All	Company	–
What a team member did in the console	Internal	User	–
What a team member did in customer accounts	All	–	Their email
Who changed team access	All	Event types for role change, 2FA reset, deletion	–

The audit trail in the console

Indicator	Meaning
Email badge under the user’s email	A team member did this with a service PIN. The badge shows their email.
Impersonated badge	The same, but the team member’s email is not available
”-” in Company	The event has no company, such as a team member’s sign-in
”-” in User Email	The event has no user, such as an admin’s edit of company details
Lower-case source such as billbee	A connected tool reported the event

The pre-filtered tab

A tab opened from a page has the person or company in its title and its filters already set. Why: several questions can stay open side by side, each in its own tab.

The Marketplace Editor’s view

A Marketplace Editor sees the logs of one partner user at a time, with the user filter locked.

What this screenshot shows

Screen: Logs
Highlighted: “Felix Braun (felix.braun@example.com)”: none
Also visible: No actor switch, no Company filter; Five events of Felix Braun
Purpose: the restricted Marketplace Editor view

A Marketplace Editor reaches the Logs only through View Logs on a Marketplace partner user’s page. The tab shows that partner’s events only.

The actor switch and the company filter are hidden, and the user filter is locked to the partner. Source, type, date and search work within those events. Opened any other way, the Logs show a no-access card. Why: the Marketplace Editor role reviews what partners changed on their cards, not customer activity.

The payload

The "Event payload" dialog of the role change of lukas.hartmann@example.com. The formatted JSON reads "ActingAdminEmail": "jonas.becker@example.com", "NewRole": "MarketplaceEditor", "PreviousRoles": ["MarketplacePartner"]. The roles appear with their technical names, not their labels. The highlighted "Copy to clipboard" button at the bottom left copies the JSON. — The payload of a role change names the admin, the new role and the previous role.

The payload is the JSON written with the event, shown as stored. Field names are technical, such as ActingAdminEmail, NewRole and PreviousRoles. Roles appear with their code names, which Staff roles and what they can do lists next to each label.

Sign-in payloads contain browser, operating system and device. Tool events contain what the tool sent. Why: the payload turns “a role changed” into “Jonas Becker moved Lukas Hartmann from Marketplace Partner to Marketplace Editor”.

Event sources

Source as filtered	Source as shown in the list	What it records
Commerce Hub	Commerce Hub	Everything that happens in comrce Hub itself
Amainvoice	amainvoice	Events reported by Amainvoice
Billbee	billbee	Events reported by Billbee
Replyco	replyco	Events reported by Replyco
Ventory One	ventoryone	Events reported by VentoryOne

Tools may report event types of their own. Those show their technical name instead of a label. A tool event always belongs to a company.

Event types and their labels

These are the event types in the Event Types filter, grouped by area. Each group says whether customers see the types in the Logs of their own account. The search also matches each type’s technical name, such as UserActions.LoggedIn.