How do I keep an audit trail of who accessed or changed a document?
Use FormKiQ document/user activity and resource activity APIs alongside configured AWS logs to investigate operations. Verify which actions your installed deployment records, how long evidence is retained, and who can read or alter exports. Application history, CloudTrail, and CloudWatch cover different events; none should be assumed to record every content view, workflow decision, or external integration automatically.
Choose the evidence source
Use GET /documents/{documentId}/userActivities for one document, /userActivities for user-oriented queries, and /activities for broader resource activity. Apply site and supported filters, then follow pagination so exports are complete.
AWS CloudTrail records supported AWS service activity according to its configuration. CloudWatch contains configured application/service logs and metrics. Neither is an automatic substitute for the application's business-decision history.
Verify coverage and retention
Perform a representative upload, metadata change, content access, workflow decision, and deletion in a test site. Inspect which evidence source records each event, including identity, time, resource, and outcome. Direct access through an already issued content URL may have a different evidence path from an API call.
Define log retention, export schedule, restricted access, backup, and integrity controls. Protect audit exports as potentially sensitive records. Re-run coverage tests after upgrading or changing storage/delivery paths rather than promising a universal audit trail from a feature name.
Edition and configuration
Activity/reporting availability and fields depend on the backend and installed capabilities. AWS logging, retention, protected export storage, and any audit evidence requirements need deployment-specific configuration.