Skip to content

Audit log

The audit log is the shared, read-only record of what happened in Lurana: who did it, to which case, process, or document, and when. It comes from the same service that powers the Dashboards tab.

BPM embeds the Explorer in Admin → Audit Logs. DMS keeps its own audit log; that log is documented with Lurana DMS.

Who this guide is for

  • Auditors — trace activity, investigate a case, export evidence.
  • Support and operators — find out what happened to a case or a process.
  • Administrators — review access and changes across the workspace.

What you can do

Goal Where
Search individual audit rows Explorer
Investigate one case end to end Cases
Study a process lifecycle Processes
Watch a live activity preview Real-time monitoring

Where it appears

Surface How to open it Scope
BPM Admin → Audit Logs → Explorer the shared audit log
BPM Admin → Audit Logs → Emails email-specific log, see Emails
Standalone service the audit application URL adds Cases, Processes, and Real-time monitoring

Explorer is the real audit log

Explorer is the primary surface. Emails is a secondary, email-specific audit log that ships with BPM: it answers was this email sent?, not what happened to this case?.

Start here

  1. Getting started — open the service, understand your workspace, and take the first tour.
  2. Core concepts — the vocabulary used across the screens.
  3. Navigation and common controls — date ranges, process and team filters, refresh behavior.
  4. Settings and preferences — timezone, language, theme, and session behavior.
  5. Exports — what a CSV includes and how it is scoped.

Then work through the log:

A note on preview pages

Preview pages

Real-time is a preview page built with sample data. It is not backed by your workspace data yet, so do not use it for compliance evidence.

Data and privacy

  • The audit service is read-only: it never changes cases, processes, or documents.
  • Every query is scoped to the workspace you opened from Luos.
  • Timestamps are stored in UTC and displayed in the timezone from your Lurana session.
  • Exports can contain user names, roles, and IP addresses. Handle them according to your organization's data policy.

Comments are enabled at the bottom of every page. Use them to flag unclear steps or missing information.