Core concepts¶
The same vocabulary appears on every screen. This page defines the terms; see the Glossary for a compact list.
Audit event¶
A single row in the audit log. It records who did what, when, to which object, and with which outcome. Everything in the dashboard is built from these rows.
An event typically includes:
- timestamp (UTC in storage, your timezone on screen)
- event type and action
- actor (user ID, username, role)
- process, case, task, and object identifiers
- outcome (for example success or error)
- session type and client information
Workspace¶
An isolated tenant. Every query is scoped to one workspace, and switching workspace switches the data.
Event type¶
A dotted identifier that groups related events, usually by object:
| Prefix | Covers |
|---|---|
process.* |
Process creation, updates, deployment, and lifecycle |
form.* |
Form activity inside a process |
task.* |
Task assignment, completion, and routing |
case.* |
Case creation, activation, pause, completion, deletion |
| authentication events | Sign-in and session activity |
The exact set of event types comes from your workspace data.
Process¶
A BPM process definition or instance. A process has a name, a process ID, and a process UID. The Processes page uses these to find and summarize the process lifecycle.
Case¶
A business case handled by a process. A case has a case number (for example
APP_001) and a case UID, plus a status such as draft, active, in
progress, paused, completed, or cancelled.
Cases are the unit auditors usually investigate: you search one case number and see every event that touched it.
Task¶
A step inside a case. Tasks are assigned, routed, completed, or reassigned; each of those actions produces audit events.
Actor, user, and role¶
The actor is the person or system that produced an event. It is identified by a user ID and usually carries a username and a role (for example admin, manager, auditor, or designer).
Outcome¶
The result recorded for an action, such as success, error, or a warning. Outcomes help separate normal activity from failed operations.
Session¶
A period of activity for a user. The audit log records the session type (for example web or API) and a session identifier, which is useful when tracing sign-ins and automated clients.
Log level¶
A severity label on an event: info, success, warning, or error. It is used by Explorer filters and is not the same as the event type.
Timezone¶
Audit timestamps are stored in UTC. The dashboard converts them to the timezone from your Luos session for display, filtering, and export. If your session has no timezone, UTC is used.
Dashboard, plugin dashboard, and registry¶
- A dashboard is a page of cards and charts built from the audit log.
- A plugin dashboard is a dashboard delivered by an installed plugin for your workspace.
- The Dashboards registry is the read-only list of dashboards registered by the plugins installed in the application, with the owning plugin, type, department, version, and status.
Preview page¶
A page that looks complete but is fed by sample data. Real-time Monitoring is a preview and must not be used as evidence.