Document activity
Keep important document and workspace events visible as the material moves forward.
DOCUMENT ADDED · WORKSPACE UPDATE
Audit trails
See how work moved.
Keep the record clear.
A clear, metadata-only record of meaningful workspace activity: document changes, invitations and access updates, kept separate from the working content itself.
No card required.
TIMEWORKSPACE ACTIVITYACTOR
09:18＋Document added to the workspaceWorkspace owner
09:24↗Invitation acceptedInvited member
09:31◷Workspace access updatedWorkspace admin
09:46×Deletion activity recordedWorkspace owner
A clear account of change
Read the activity,
not the content.
The record helps a team understand what happened around the work, without turning workspace activity into another place where the work itself is exposed.
Access changes
See the meaningful events around invitations, membership and the access a workspace needs.
INVITE · ACCEPT · ROLE UPDATEDeletion events
Keep a clear activity record when a document, chat or workspace enters its deletion flow.
DELETE REQUEST · ACTIVITY ROWBuilt for the handover
Useful when the work
has to move between people.
Do not rebuild the story from messages, screenshots and memory. Keep the relevant activity attached to the workspace where the decision belongs.
Invite sentPENDING
Invite acceptedMEMBER
Follow access with the work.
Membership and invitation activity can sit in the same workspace as the source material and decisions it relates to.
Document added09:18
Workspace updated09:31
Keep the signal concise.
The activity record is metadata-first, so it explains the event without becoming a second copy of your documents, prompts or answers.
Delete requestedLOCKED
Activity recordedDONE
Make lifecycle events visible.
When work is removed, the activity record can still explain that a deletion event took place without retaining the deleted working content.
A scattered trail
What changed can become a reconstruction exercise.
- Updates are split between email, chat and file history.
- Handovers depend on what someone remembers to explain.
- Visibility can mean copying the working content into another place.
Zylox workspace activity
Keep meaningful activity close to the work it relates to.
- Workspace events are recorded around documents, access and deletion.
- Metadata-first activity keeps the record separate from working content.
- Reviewers can start from the workspace, not a reconstructed timeline.
More of the product
Keep the context,
not just the trail.
Audit activity is more useful when the source material, answers and people involved still have a clear place to live.
Questions
Audit trails,
in detail.
What does the activity record show?
It covers meaningful workspace activity such as invitation and access lifecycle events, document-added rows, workspace changes and deletion activity. Availability depends on the current workspace configuration and account access.
Does the record contain my documents, prompts or answers?
No. The current activity trail is metadata-only. It is designed to record the event and its context without exposing raw document content, prompts, answers or source passages.
Is this an immutable compliance audit log?
No. Zylox records useful product activity, but it is not positioned as an immutable or compliance-grade audit system. Requirements for that level of auditability should be discussed separately.
Can I use Audit Trails with a team?
It is most useful where people share a workspace and need a clearer handover or review point. Workspace membership and access are permission-based.