Activity Logs: see who did what in your account

Something changed in your account and you want to know who did it? Activity Logs are the answer. They're a timestamped, read-only record of every important action taken in your Cruva account — sign-ins, automations started or paused, samples approved, team members added, billing changes, and more. Every entry shows who did it, what they did, when, and from which IP address.

Use it for accountability: an automation was paused and nobody owns up to it, a sample batch was approved that shouldn't have been, a teammate's access changed unexpectedly, or you just want to confirm what an external collaborator or agency partner actually did inside your shop. It's also the evidence trail you need for a security review or SOC 2 audit.

Admins only. Activity Logs are visible to the account owner and to sub-accounts with the Admin role. If you're a regular User you won't see the menu items below and the page will refuse to load — ask your account admin to look it up for you. (Who's an admin? See Add team members and manage sub-users.)

Where to find it

There are three ways in. All of them land on the same page.

From the profile menu (the usual route)

1. Click your user avatar in the top-right corner of the dashboard.
2. Click User Management — or go straight to cruva.com/dashboard/users.
3. Click the Activity Logs button at the top of the Users page — or go straight to cruva.com/dashboard/audit-logs. (cruva.com/dashboard/activity-logs takes you to the same place.)

For one specific person

On the Users page, find the person's row, click the ⋯ (three dots) on the right, and choose Audit logs. The log opens already filtered to just that person's actions. This works for your own team members and for external collaborators.

From Account Settings

Click your avatar → Account Settings, scroll to the Audit logs row in the Security section, and click View audit logs.

You'll see the feature called both Activity Logs and Audit logs around the dashboard. They're the same thing. Don't confuse it with the Activity Logs tab inside an individual outreach automation — that one lists the messages an automation sent to creators, not the actions your team took. For that, see Why isn't my outreach sending?.

Finding what you're looking for

The log shows the newest actions first. Use the controls across the top to narrow it down:

• Search box — type part of an action, a target name (the automation, list, or sample request involved), or a teammate's email. It matches across all of those at once.
• User — pick a single person to see only what they did. Opening the log from the ⋯ menu on the Users page sets this for you.
• Action — pick one type of action, such as "Started automation" or "Approved sample requests," to see every time it happened and who did it.
• Platform — Web (someone clicking around the dashboard), API (your REST API key), or LLM (Copilot, or an MCP client like Claude). Handy for separating human clicks from automated or AI-driven changes.
• Date range — defaults to all time. Narrow it to the day something went wrong.

Combine them freely: "everything this user did last Tuesday," or "every automation that was paused this month, by anyone."

What each entry tells you

Each row is one action. Reading left to right:

• Time — when it happened, in your local timezone.
• Account email — who did it. For a Cruva support session or an agency-manager login, this shows their email, not yours, so you can tell the two apart.
• Account type — a colored badge: Owner, Admin, User, External (a collaborator you granted access to), Manager, Cruva staff, or System.
• Platform — Web, API, or LLM, as above.
• Action — a plain-English label like "Started automation" or "Deleted group." Hover to see the raw action code.
• Target — what was acted on, by name.
• IP — the IP address the action came from, with a country flag. Hover for the city and region. If an action came from an address or country you don't recognise, that's your cue to check the account's security.
• Details — the exact route used, how it happened (for example "via AI · create_group" or "via API key"), and any extra context for that action.

What gets recorded

Security and account events, plus the important actions across the product:

• Sign-in activity — successful logins, failed login attempts (with the reason), and two-factor authentication being enabled, disabled, or failed.
• Staff and manager sessions — when Cruva support observes your account, or an agency manager signs in, it's logged under their email, not yours.
• Product actions — automations started, paused, created, edited, or deleted; email campaigns; groups and lists; sample requests and sample rules; creator briefs; community campaigns; DMs sent; and billing changes.
• Team and access changes — inviting a teammate, changing their shop or section access, deleting them, removing them from the organization, and inviting, updating, or revoking an external collaborator.
• Shop transfers and credentials — initiating, accepting, or declining a shop transfer, and resetting Affiliate Manager credentials.
• API and Copilot actions — anything done through the REST API or through Copilot / MCP appears with the API or LLM badge, with the key or tool that did it in the Details column.

External collaborators and agency partners appear tagged External or Manager, so you can see exactly what someone outside your team did in your shop.

Common questions

I don't see User Management or Activity Logs in my menu. You're signed in as a regular User, not an Admin or the owner. Ask your account admin to check the log for you, or to upgrade your role.

Can I edit or delete an entry? No. Activity Logs are read-only for everyone, including the owner. That's what makes them trustworthy as evidence.

How far back does it go? Entries are kept for 90 days. If you need a record for a longer compliance window, review and save what you need before it ages out.

Something happened but it isn't in the log. The log records the important state-changing actions listed above. Routine browsing and read-only views aren't logged. If you believe an action that should be there is missing, contact support with the date and what you expected to see.