Start with a task's history
Read the saved run or chat to identify which tool was called, which action needed approval, and what result was returned. A task's reported outcome should be checked against the external destination for consequential writes.
Know what evidence you need
List the events your organization must retain, who needs to read them, and the required retention period. A readable chat history is not automatically a complete compliance audit export.
Confirm enterprise requirements
If your organization needs a dedicated customer audit export, SSO integration, or a particular retention agreement, discuss those requirements with the team. Use the Security and legal pages for published Spinrun policy.
Handle logs as sensitive data
Logs can reveal record identifiers and business context. Share only the material needed for a review and avoid sending credentials. Keep the original task reference with a support request.
Open the relevant screen
Use Audit logs and activity in the active workspace. Sign in if needed. Check the workspace name before changing shared settings, connections, or billing.
If a control is unavailable, ask the workspace administrator or contact support. Include the screen, the action you tried, and the approximate time. Keep credentials and private customer material out of the request.