Skip to main content

Activity and Security Visibility

Sol Helps includes activity logging and a security.read_audit permission, but the repository does not establish a complete, immutable, compliance-grade audit trail for every workspace action. Do not use this page as a retention or legal assurance.

What can be verified​

Dashboard code records selected events such as account-settings views and team invitations with a type, summary, visibility, data classification, and bounded metadata. Security Admin includes security.read_audit; Owner and Admin inherit that permission.

Event coverage, an end-user retention guarantee, tamper resistance, and export completeness cannot be verified from the current documentation source set.

Distinguish the records​

  • Activity events describe selected workspace actions.
  • Captured Questions contain eligible conversation evidence.
  • Signal Health contains operational capture and performance measures.
  • Insights aggregate heuristic evidence patterns.
  • A savedAt timestamp on another object proves that object was saved, not who performed every preceding action.

Investigate an important change​

  1. Record the observed change, workspace, affected assistant, and time window.
  2. Review the available activity view if your role permits it.
  3. Check the current team role and assistant scope.
  4. Correlate with the affected configuration or object; do not infer causality from a nearby analytics event.
  5. Preserve relevant identifiers and request IDs before escalation.

For access policy, see Roles and Permissions. Ask Sol Helps support for current event coverage and availability before relying on activity data for a formal control.