# The audit log: who did what in your workspace

Source: https://frosvo.com/docs/audit-log
Updated: 2026-10-22

Owners can review sign-ins, security changes, team and API-key changes, integrations, privacy and billing actions, and anything Frosvo support did, then filter or export them as CSV.

When something changes and nobody remembers why, the audit log answers who, what and when.

## Open it

Go to **Settings → Security** and open **Audit log**. You must be an owner.

## What is recorded

- Sign-ins, and changes to passwords and two-step settings.
- Changes to the team, ownership and invitations.
- Creating API keys and webhooks.
- Integrations and privacy settings.
- Billing actions.
- Anything Frosvo support did while helping you.
- Problems you acknowledged, resolved or ignored on the Problems page.

## Find an entry

Use the filters to narrow by person, kind of action or date. Each entry shows who did it, what they did and when.

## Export

Download the log as **CSV** to keep a record or give an auditor. Entries are kept for **400 days**, so export before that if you need longer.

## Emails to owners

Owners are also emailed about important changes: someone made an owner, two-step turned off, a new API key or webhook, the workspace handed over, and whenever Frosvo support opens your workspace.

## Good habits

- Look at the log every month for changes you do not recognise.
- After someone leaves, check what they changed.
- Keep an export before major changes such as a handover.

Read the [security overview](/docs/security) for the rest of the protections, set up [two-step sign-in](/docs/two-step-sign-in), and control who can change what with [roles](/docs/roles-and-permissions). Data handling is in [your data](/docs/privacy).

## Common questions

**Does the log show what the change was?** Each entry says who did what and when. For a deeper look at a change, compare it with the setting itself and ask the person.

**Can I stop people seeing it?** Only owners can open the audit log, and it cannot be given to a custom role, so you do not need to hide it.

**How do I use it after an incident?** Filter by the day it happened, then look for sign-ins, key or webhook changes and team changes around that time.

## Common questions

### Who can see the audit log?

Owners only. It cannot be given to a custom role.

### How long is it kept?

Entries are kept for 400 days.

### Can I export it?

Yes, as CSV from the audit log page. Developers can also read it through the API with the audit scope.

### Is Frosvo support recorded?

Yes. Anything support does while helping you appears in the log, and owners are emailed each time support opens the workspace.
