Activity Logs provide a tamper-evident audit trail of all significant actions within a Docupath tenant - spanning document lifecycle events, configuration changes, and user administration actions. The module serves as the single source of truth for answering "who did what, and when" across the platform.
Activity Logs supports date range filtering, keyword search, and expandable detail views that reveal before/after values for configuration changes. Activity Logs are essential for compliance reporting, troubleshooting, and maintaining operational accountability.
How It Works
What Is Captured
Activity Logs track actions that change system state or have compliance relevance, organized into three categories:
Document Lifecycle Events
Document uploads, approvals, rejections, and reprocessing
Trading party assignments and changes
Document status transitions
Configuration and Security Changes
System Settings updates (branding, retention, duplicate handling)
API credential creation, rotation, and deletion
Instruction Build, Transformation Rule, and Rejection Rule changes, including enabling and disabling an individual instruction or rule.
Customize captured fields configuration changes
User Administration
User creation, role assignments, and profile edits
Invitation status changes
Organization-level user mapping changes
Interface Overview
Activity Logs are accessed via Main Menu → Activity Logs and provide:
Feature | Description |
Search Bar | Look up events by user, keyword, or action type |
Expand Control (▾) | Reveals structured details including before/after values for changes |
Log entries are copy-friendly, making them suitable for inclusion in support tickets, audit notes, or compliance reports.
Searching and Filtering
Date Range: Start with a narrow range (e.g., 7 days) and expand if needed - broad ranges may return large datasets
Keyword Search: Search by action keyword (e.g., "Approve", "Role", "Retention") rather than only by person for more targeted results
Expand Details: Always click the expand control (▾) to reveal before/after values, which provide critical context for understanding changes
Supported Configurations and Options
Configuration | Detail | Date range filtering | Custom date range selection |
Keyword search | Free-text search across user names, action types, and event descriptions | Detail expansion | Before/after value inspection for configuration changes |
Copy support | Log entries can be copied for external use | Access control | Available to Admin and Manager roles |
Other Technical Specifications
Parameter | Detail |
Retention | Tied to the tenant's data retention policy |
Export | Manual copy from interface; no built-in bulk export |
Integration Points
All platform modules: Activity Logs capture events from across the entire tenant - document processing, rule configuration, user management, system settings, and API credential management
Compliance reporting: Provides the audit evidence needed for internal reviews, external audits, and regulatory compliance
Troubleshooting: Enables investigation of unexpected outcomes by tracing the sequence of actions and configuration changes that led to the current state
Data retention: Log retention is governed by the tenant's data retention policy set in System Settings
Notes
Activity Logs record who, when, and what - they do not capture full system-level diagnostic traces or performance metrics
Log retention is tied to the tenant's data retention policy; for long-term compliance, critical entries should be saved or exported to an internal audit repository
There is no built-in bulk export feature - entries must be copied manually from the interface
Searching with very broad date ranges may return large result sets; start with narrow ranges for faster analysis
Searching by person alone may miss relevant events - combine with action keyword searches for comprehensive results
Before/after values are only available for configuration changes; document lifecycle events show the action but not field-level detail
A rule or instruction that is disabled produces no processing entries, because it is skipped before evaluation. Its absence from a document's trail is expected and is not evidence that processing failed. The act of disabling it is itself recorded as a configuration change, so use the configuration history to find out when it was disabled and by whom.