SimpliServDocs

Activity log

Trace who created, changed or deleted which object in SimpliServ and when — with a before/after comparison, filters and privacy masking

→ Open logs in SimpliServ

The activity log automatically records who created, changed or deleted which object in SimpliServ and when. Each row shows the user, the action, the affected object and – for changes – the old and new values. That keeps it traceable how data has changed over time.

The log is only visible to users with the View activity log permission (admin.activity-logs.view). See Users & roles.

Open the log

In the left-hand navigation, under Administration, go to Logs.

The newest entries are at the top – the table is sorted by timestamp descending by default.

The columns

Each entry consists of the following fields:

  • User – who triggered the action. For actions without a logged-in user, the field stays empty.
  • Action – shown as a coloured badge:
    • Created (green) – a new object was created
    • Updated (blue) – an existing object was changed
    • Deleted (red) – an object was removed
  • Object – the type and ID of the affected record, e.g. Invoice #842 or Customer #17.
  • Timestamp – the date and time of the action.
  • Old values – the values before the change (for "Updated" and "Deleted").
  • New values – the values after the change (for "Created" and "Updated").

Old values and new values show, for "Updated", only the actually changed fields as a before/after comparison. For "Created" or "Deleted", the created or removed record is recorded. Long contents are shown scrollable in the cell.

Via the column menu you can show or hide columns. The ID column is hidden by default.

Filtering and sorting

Filter by user

Open the filter in the User column and choose one or more people to see only their actions.

Filter by action

Via the Action filter you narrow down to Created, Updated or Deleted – multi-select is possible.

Sort

Click a column header (e.g. Timestamp, User or Action) to sort the list by it.

What is logged?

SimpliServ automatically logs changes to the central business objects – including e.g. customers, leads, proposals, orders, delivery notes, invoices, payments, products, warehouses, tasks, employment contracts, leave requests as well as location and settings records. For each of these entities, creating, changing and deleting automatically triggers a log entry.

Additionally, for each entry the IP address, browser identifier and the accessed URL are also stored in the background.

Changes to an object's custom fields also appear in the log – as their own before/after comparison.

Privacy: what doesn't appear in plaintext

Sensitive fields aren't logged in plaintext:

  • Passwords, remember tokens and tokens aren't recorded at all.
  • Values in fields like password, token, API key and secret are shown masked (••••••••).
  • Long rich-text contents (e.g. email texts) are shortened to a brief plaintext preview instead of storing the raw content.

Technical "phantom changes" – e.g. when a decimal value like 39,90 and 39.9 produce the same database value – are filtered out and don't create an entry.

Notes

  • The log is read-only: entries are created automatically and can't be edited afterwards in the interface.
  • The data is stored isolated per tenant. More on the architecture and privacy is under Security.
  • Users & roles — assign the admin.activity-logs.view permission to unlock the log.
  • Security — how SimpliServ isolates and protects data per tenant.
  • GoBD archiving — audit-proof archiving and retention of your documents.
  • BAO compliance — which legal requirements SimpliServ covers technically.

How is this guide?

On this page