Event Log
An organisation-wide history, visible only to System admins, that records security and system events such as users being created or collections being deleted.

is a time-stamped history of recorded events across your Kinabase workspace, including user sign-ins, Field

Field

A single piece of information stored on every record in a Collection, such as text, a number or a date, similar to a column in a spreadsheet.

changes, and the creation or deletion of Record

Record

An individual entry within a Collection, like a row in a database table, representing one item or entity such as a customer or an order.

Unlike Activity

Activity

A logged event or note on a record — such as an email, phone call or meeting — that builds up a timeline of interactions over time.

entries, which are added by your team, Event Log entries are generated automatically by Kinabase. They help System admins review what happened, when it happened and which user performed the action, where that information is available.

Event Log is available on the Pro and Max plans. If you're on Starter and need it, see Billing & your plan to upgrade.

1. Accessing the Event Log

Go to Settings → System → Event Log.

Only System admins can view the Event Log.

2. Reading the timeline

Events are listed as a timeline, most recent first. Load more at the bottom brings in older entries.

Event Timestamp

Events are listed in reverse chronological order (most recent first) with exact date and time.

Event Type

Descriptions like 'User Successful Sign In', 'Collection Field Updated', or 'Record Deleted'.

User Details

Shows which user performed the action - plus the IP address and browser user agent for sign-in events.

Collection & Field

Identifies which collection or field was changed, if applicable.

For example: "User Successful Sign In" lists the user's name, IP address, and browser agent. "Collection Field Added" details which collection was modified and by whom.

3. Common uses

Security audits

Confirm only authorised people accessed the system, or spot suspicious sign-ins.

Change tracking

Identify who altered a field or record, and when.

Compliance

Use the Event Log as supporting evidence during an internal review or audit. Check that the events recorded and the available history meet your organisation's own audit and retention requirements.

4. Event Log vs. Activities

Both keep a history of what happened, but at different scopes:

Activities are a record-by-record timeline, added by your team as notes, calls, or updates. See Activity logs.
The Event Log is a workspace-wide, automatically generated audit trail of security and system events. Use it when you need to know who changed something, or when a security event occurred, anywhere in your organisation.

Tips

Restrict Event Log access to only those who need it, keeping the audit trail itself secure.

For day-to-day tracking, Activities give you a timeline within each record; the Event Log gives you a higher-level, workspace-wide view.

Check the Event Log periodically - weekly or monthly - for anomalies.

The Event Log helps your team investigate changes and review security events across your Kinabase workspace.

Need more help? Ask your System admin, or contact our support team via Help & Support.

PreviousTelemetry

Next Data Visualisation Tools