If you’re coming from RB2B
RB2B does not expose a team-facing audit trail, so there’s no equivalent screen to map from. The Activity log is closest to what you’d otherwise reconstruct from support tickets and memory.| What you want to know | RB2B | Squid ID |
|---|---|---|
| Who changed a setting | Not surfaced | Logged with actor, target, and timestamp |
| Who revealed a given visitor | Not surfaced | Logged per reveal, with credit cost |
| Team and role changes | Not surfaced | Invites, role changes, removals, ownership transfers |
| Billing and refund events | Support only | Status changes, match flags, refunds in-line |
| Export for compliance | Not available | One-click CSV, dated |
Why this matters. Visitor identification tools rarely ship an account-level audit trail. If your team shares a login or you answer to a security review, the gap shows up the first time you need to explain a change after the fact.
What gets recorded
Every mutation a teammate makes is logged as a single event. Each entry captures four things:- Who: the actor’s email.
- Action: what they did (revealed a visitor, updated settings, invited a teammate, connected Slack, and so on).
- Target: the thing the action touched (the visitor, the teammate, the site, the ICP).
- When: a timestamp, shown as relative time in the list.
- Reveals: visitor reveals (manual, automatic via Squid ID+, and admin), plus profile actions like hide, unhide, mark not-a-bot, dismiss bots, and delete.
- Team: teammate invites, role changes, removals, and per-site sharing (add admin, add viewer, change role, transfer ownership, remove).
- Settings: account settings, per-site settings, add-ons, ICPs, saved filters, notification preferences, webhooks, and onboarding completion.
- Integrations: Slack connect and disconnect, Slack channel routing changes, and notification channel events.
- Billing: account status changes such as pause, cancel, resume, reactivate, and delete, plus match flags and refund-related events.
Only your team’s actions appear here. Squid ID support access is recorded in a separate internal trail and is not shown in your Activity log.
Category tabs
Across the top of the log, tabs group related actions so you can answer “who flipped X recently?” without scanning everything. Each tab shows a count of matching events.- All
- Reveals
- Team
- Settings
- Integrations
Time range
A time-range selector filters the list to a recent window:- All time (default)
- Last 24 hours
- Last 7 days
- Last 30 days
Search
A free-text search box filters events as you type. It matches across the action label, the actor’s email, the IP, the target or subject (visitor name, teammate email, Slack workspace), and the names of any changed fields.The tabs, time range, and search apply to the events currently loaded in the view. Scroll down to load older events, then your filters apply to the larger set.
CSV export
Use the Export menu in the page header to download the log as a CSV. Each row includes the timestamp, actor, action, target, IP, and a serialized copy of the event details. The file is named with the current date, for examplesquid-activity-2026-06-21.csv.
This is the export to hand to an auditor or attach to a compliance review.
Retention
Entries are kept for roughly one year. The audit log uses a TTL index set to 365 days, so Mongo auto-prunes anything older. If you need a longer record, export to CSV before events age out.Why it matters
- Accountability across a team. When several people share an account, the log answers who changed a setting, who removed a teammate, and who revealed a given visitor.
- Tracing a change or a refund. A surprise in your settings or your balance has a recorded actor, target, and timestamp behind it.
- Compliance. The CSV export gives you a portable, dated record for security reviews and audits.