Audit logs
Audit logs are Rival’s memory: a record of what happened across your organization — who did what, when, and to what. When governance is about deciding what’s allowed, audit logs are about proving what actually occurred.
What’s tracked
Section titled “What’s tracked”Logs capture the activity that matters for accountability: user actions, agent and workflow runs, approvals granted and denied, connector usage, and administrative changes. The result is a trail you can follow from an outcome back to its cause.
Compliance reporting
Section titled “Compliance reporting”For regulated organizations, “we think it’s fine” isn’t enough — you need to show it. Audit logs turn AI activity into evidence: reports that demonstrate approvals happened, policies were enforced, and access was controlled. This is often what makes AI adoption approvable by risk and compliance teams in the first place.
Investigations
Section titled “Investigations”When something looks wrong, logs are how you find out what happened. You can trace a specific action back through the workflow that produced it, the approval that let it through, and the person or agent behind it — turning “how did this happen?” from a mystery into a lookup.
Who can see them
Section titled “Who can see them”Audit logs are an admin-level view. Team members don’t see organization-wide logs, though they see their own activity. See the Capability matrix.
A quick example
Section titled “A quick example”A customer reports receiving something they shouldn’t have. An admin opens the audit log, finds the workflow run, sees which agent acted and that an approval was mistakenly granted, and fixes the approval rule — with a complete record of exactly what occurred.