Skip to main content

Configuration - General - Activity Log

Updated over a week ago

The Activity Log provides a central overview of all actions and system events within Zero Friction. This log records what happened, when it happened, and, if applicable, who performed the action.

You can find the Activity Log via:
Configuration → General → Activity Log

The Activity Log is important for:

  • auditing and compliance;

  • insight into system behavior;

  • analyzing changes and events;

  • support and troubleshooting for questions or incidents.


What does this part show?


The Activity Log displays a table of automatically recorded activities within your organization. Each line represents one system activity.

The log includes activities for:

  • generating invoices;

  • creating or uploading documents;

  • sending communications (e-mail, SMS, e-invoicing);

  • meter installations;

  • processing of relocation requests;

  • other automated system processes.

Activities are read-only and are recorded chronologically. You will only see activities performed within your own organization.


Layout

Activity overview (table)


The table in the Activity Log contains four columns:

  • Subject
    The type of entity to which the activity relates, such as:

    • Invoice

    • Customer

    • Contract

    • Document

  • Action
    The type of action performed, for example:

    • InvoiceGenerated

    • DocumentCreated

    • CommunicationStarted

  • Date
    The date and time the activity took place.
    The display depends on your locale settings.

  • Contents
    A button (code icon) that allows you to open the technical details of the activity.


Actions

Within the Activity Log, the available actions are limited:

  • Viewing activities
    You can view all visible activities within the set filters.

  • Viewing payload details
    The payload button opens a side panel with additional technical information in JSON format.

It is not possible to manually create, modify or delete activities.


Behaviors & Logic

  • Activities are created automatically by the system.

  • For each relevant event, a new activity is immediately registered.

  • One event can generate multiple activities.
    For example, generating an invoice can lead to activities on:

    • the invoice;

    • the linked customer;

    • the accompanying contract.

  • The Activity Log works in real-time: new activities appear immediately after an event occurs.

  • The log is organization-specific; activities of other organizations are never visible.


Problem

Solution

Activity log is not visible in the menu

Please check if you have Activity Read Feed permission

Activities are missing

Check the date range and subject filter set

Activities seem outdated

Remove filters or check if recent events have actually been executed

Payload cannot be opened

Try refreshing the page or check your browser settings


Why don't I see the Activity Log?
You are probably missing the required Activity Read Feed permission.

Can I export activities?
No, there is currently no export functionality available.

How long are activities retained?
The retention period depends on the system configuration. Contact your administrator for details.

Can I delete or correct activities?
No, activities are read-only and part of the audit trail.

Why do I see multiple activities for one invoice?
Because the same event is logged on multiple entities (invoice, customer, contract).

What's in the payload?
Technical metadata such as entity IDs, event data, and system information. The content varies by action type.

Why do I miss certain activities?
Check that:

  • the correct date range is selected;

  • the correct subject type has been filtered;

  • the activity was actually carried out within your organization.


  • Activity
    Automatically recorded system event within Zero Friction.

  • Activity Entry
    One separate line in the Activity Log.

  • Subject
    The entity type to which the activity relates.

  • Action Type
    The specific action or event that occurred.

  • Payload
    Technical additional information of an activity in JSON format.

  • Originator
    The user or system process that caused the activity.

  • Audit trail
    Immutable logging of events for auditing and compliance.

  • Filter
    Setting to limit the activity overview by date or subject type.

  • Pagination
    Splitting large datasets into multiple pages for better performance.

Did this answer your question?