Record Activity
What This Service Is For
Record Activity retains visits and supported business activity within each workspace. It lets people inspect their own navigation history and lets authorized administrators inspect another person’s visits.
Boundary
Audit owns the shared activity store and writer functions. Security maintains a separate security history. Queries uses the activity account to find current readable records, while each publisher defines the meaning of its business events.
Operations in Words
Reporting requires an occurrence key and a registered target. Current target read and dataset authority are resolved before insertion; a repeated same-target key returns the old event, and changed-target reuse causes conflict.
Personal history and administrative history use distinct permissions. They return visit events only, newest first, with twenty-five rows by default and a maximum of fifty. Every operation states why it is unpublished to Submissions.
Events and Jobs
No business-event transport or job is declared here. Other modules use in-process activity writers, and workspace deletion invokes bounded activity purge.
Consistency Guarantees
Workspace policies and ordinary application privileges protect stored events. Event insertion is transactional, but target resolution happens first. Mutation atomicity requires the owner’s transaction. Client delivery can lose visits, and retention beyond workspace removal still lacks a decision.