Skip to main content

​
Event and Activity Model

Source: equa-server/modules/activity/, equa-server/modules/persistence/src/schema.ts

​
Overview

Equa tracks user activity through three complementary mechanisms:
  1. Actions — High-level user actions within organizations
  2. Event Logs — Detailed event records with JSON payloads
  3. Tasks — Workflow status tracking for multi-step operations

​
Entities

​
Actions

Source: equa-server/modules/persistence/src/schema.ts (Actions entity) Tracked via equa-server/modules/activity/ and surfaced in the organization dashboard.

​
Event Logs

Source: equa-server/modules/persistence/src/schema.ts (EventLogs entity) Event logs capture granular platform activity with structured JSON payloads for audit and debugging purposes.

​
Tasks

Source: equa-server/modules/persistence/src/schema.ts (Tasks entity) Used for tracking multi-step operations like option exercises (TasksExerciseOption).

​
Activity Flow

​
Frontend Display

The organization dashboard (equa-web/src/modules/organization-dashboard/) displays recent actions for the active organization, providing visibility into team activity.

​
Audit Trail Gaps

The current event logging system does not provide:
  • Immutable log storage (logs can be deleted)
  • Comprehensive coverage of all state changes
  • Structured audit trail with before/after states
  • Log export or compliance reporting
These gaps are documented in the Compliance: Audit Trail Design specification.