Last reviewed Sep 6, 2026
If your organization is facing a formal audit and Launch is in scope, Logs is almost always the right starting point.
A reasonable approach
- Identify the specific time window and questions the audit is asking about.
- Filter Logs to that scope by actor, module, action, and date. See Filtering logs by actor, module, action, and date.
- Export the filtered result as a clean record. See Exporting logs.
- Use the permission matrix to answer any question about who could or couldn't do a specific action during the period in question.
- If the audit involves data handling or compliance specifically, see Data retention and deletion requests and Sub-processors and DPAs.
Why Logs holds up to an audit
Because Logs is append-only and every meaningful action is recorded with an attributed actor, action, target, and time, it holds up well to exactly this kind of scrutiny without needing extra reconstruction.