Activity log

In the activity log you see what has changed in Tillor, when, and by whom. You open it on a customer, invoice, task or other record, and centrally via Audit log if you have the permission for it. It is a read-only trail that you use to check or prove something.

Viewing the activity logCopy link to this section

In the app this is usually called Events or Activity, depending on where you are. Anyone with the View audit log permission can also open a central overview via Audit log in the sidebar (above Settings), with filters on user, event type and date.

For each activity you see in the timeline:

• Title - kind of event (e.g. "Invoice booked", "Customer updated")
• User - the colleague who performed the action (or Tillor for automatic actions)
• Time - date and relative time
• Description - additional details; sometimes with links to related invoices or other records
• Before / after (sometimes) - when creating, changing or deleting customer, contact, invoice, payment, payment mandate, payment group, document, access method, access point, controller, terrain, meter, meter reading, product, occupation, task or comment data, plus scanning, assigning or unlinking an identity document and changes to settings, membership rights, invoicing or NFC: which fields were changed. PIN codes of access points and personal data of an identity document are not kept in the log
• Attachments (sometimes) - downloadable files, for example for failed integrations
• Login / logout - when a colleague logs in or out, visible in the central audit log overview
• OAuth apps and consent - creating, changing, deleting or rotating the secret of OAuth apps, plus consent given, refused or revoked; visible in the central audit log overview. Client secrets are not kept in the log
• Management and security - changes to the organisation profile (name, legal details, VAT, IBAN, logo, maintenance mode), invitations and new members, personal API keys (create, change, renew, delete), ended sessions, webhooks, automations, colleague groups, terrain types, meter cabinets, controller groups, installed or removed integrations and the acceptance of the data processing agreement; visible in the central audit log overview. Keys, webhook secrets and integration settings are not kept; for an integration you only see which settings were changed
• Access to personal data - who opened or downloaded a document, viewed or downloaded the images or files of an identity document, or opened the PDF of an invoice or sent it to the tablet. Opening repeatedly within ten minutes is recorded once; every download of an identity document is recorded separately

Activity per recordCopy link to this section

On detail pages you see a timeline with the activity for that record. On the Events tab of a customer you find all activities linked to that customer (invoices, payments, occupations, etc.).

For reservations this includes creating, checking in and checking out, cancellations and related reversals, and updating reservation details.

For payment groups you also see which payments were added to or removed from a group, and for controllers which adoption requests were approved or rejected.

For payment reports this includes creating the report, finalising a draft report and sending it to the accounting system.

For signing requests you see every step: created and changed, sent, link (re)sent, reminded, signing page opened, code sent or entered incorrectly, signed, refused, reset to draft, cancelled, expired and completed. See Evidence and validity.

For external notifications you see when a linked system updated or deleted a notification it had registered.

Who did it?Copy link to this section

Next to the user, every line also shows what kind of actor performed the action: a logged-in user, an API key, an OAuth connection, an automation, the Tillor connector or the system itself. For an API key or OAuth connection, the id of that key or connection is in the details, so that with a leaked key you can see exactly what was done with it. If it says Unknown, Tillor could not determine the actor; that is deliberately something different from "System".

Security eventsCopy link to this section

Failed sign-ins, rejected API keys and OAuth tokens, refused access (missing permissions), exceeded request limits and a Tillor administrator opening your organisation are also shown in the activity log, with IP address and browser. Members with the Security alerts permission receive a notification every hour when webhooks, API keys or automations have been changed or when access has been repeatedly refused.

The access you give Tillie to your account or revoke, and every change you confirm through Tillie, are listed here too.

Exporting for an auditCopy link to this section

With Export in the activity log you download all lines of the chosen period (by default the last 30 days, at most one year) as a ZIP with the data file (CSV or JSON Lines), a manifest.json with the number of lines, the period, who exported and the SHA-256 checksum of the data file, and a CHECKSUMS.sha256 file that you can verify with sha256sum -c. The export itself is also recorded in the log, with the same checksum. Opening the full activity log and bulk exports of customer data (customer list, access log, terrains, meters) are logged as well.

All times are stored in UTC on servers with NTP time synchronisation and shown in your time zone; the export contains ISO 8601 times in UTC.

What do you use the log for?Copy link to this section

• Checking - finding out which colleague booked an invoice or changed a customer
• Troubleshooting - finding out when an error occurred
• Audits - keeping a complete trail for internal or external checks

See alsoCopy link to this section