Bitwarden Event Log Review
Overview
The event log is the organization's audit trail: logins, item access,
member and policy changes. It is the only place the Public API shows what
people did, as opposed to what they are allowed to do.
bitwarden_events_list is admin-gated in Conduit. It needs the admin
tier in the gateway access editor. If the call is denied, say that the event
review could not run; do not substitute guesses from the other tools. The
lookups this skill uses to put names to IDs are read tier:
bitwarden_members_list, bitwarden_members_get, bitwarden_groups_get,
bitwarden_collections_get and bitwarden_policies_list.
Anti-triggers
Key Concepts
Request shape
| Parameter |
Use |
start, end |
ISO 8601 range. Default is the last 30 days. Over 367 days is rejected. |
actingUserId |
Events performed by one Bitwarden account (the member's userId, not their member id) |
itemId |
Events about one vault item |
secretId, projectId |
Events about one Secrets Manager secret or project |
continuationToken |
The token from the previous page, passed back unchanged |
Only one of actingUserId, itemId, secretId, projectId per call.
What an event carries
Each event has a numeric type, a date, and, depending on the type,
IDs such as actingUserId, memberId, itemId, collectionId, groupId
or policyId, plus ipAddress and a numeric device client type. There
are no names: resolve IDs with the read tools (members by userId or id,
groups and collections by ID). Vault item names are encrypted and cannot be
resolved; report the itemId.
Event types worth watching
| Type |
Event |
Why it matters |
| 1000 |
User logged in |
Baseline; unusual IPs or times stand out |
| 1002 / 1003 |
User updated / disabled two-step login |
1003 on an owner or admin is urgent |
| 1005 / 1006 |
Failed login / failed two-step login |
Clusters suggest password spraying or a stolen master password |
| 1007 |
User exported their vault |
Possible data exfiltration |
| 1107 |
Item viewed |
Who looked at a credential |
| 1108 |
Item password viewed |
Stronger signal than 1107 |
| 1111 |
Item password copied |
The value left the vault UI |
| 1500 / 1501 |
Member invited / confirmed |
Who added whom |
| 1503 |
Member removed |
Offboarding evidence |
| 1511 / 1512 |
Member revoked / restored |
A restore after a revoke deserves a reason |
| 1600 |
Organization settings edited |
Confirm the change was expected |
| 1602 |
Organization vault exported |
Everything shared may have left |
| 1700 |
Policy edited |
Resolve policyId against bitwarden_policies_list |
These codes follow Bitwarden's event list. Check the full catalogue on
Bitwarden's event logs page before
you rely on a type that is not in this table.
Common Workflows
Periodic activity review (monthly)
- Call
bitwarden_events_list with start and end covering the month.
Page with continuationToken until it is null.
- If a page comes back
truncated, do not page on (that skips the dropped
events); re-run that stretch with a shorter window.
- Group events by type. Report counts for the watch-list types, and list
every 1003, 1007, 1602 and 1700 event individually with the acting
member resolved by name.
- Look for failed-login clusters (1005, 1006): same account many times, or
many accounts from one IP.
Answering "who did X?"
- Who changed a policy? Range around the change, filter nothing, keep
type 1700 events, resolve
actingUserId to a member.
- Who touched this item? Use
itemId with a range covering the period
of interest; keep 1107, 1108, 1111.
- What did this person do? Use
actingUserId (their userId).
Output
Lead with any urgent events (2FA disabled on an admin, vault exports, policy
changes nobody expected). Then a counts table by type, then the detail. Put
IP addresses and device details in the technical appendix, not the summary.
Gotchas
- Paging is manual. The tool never follows
continuationToken itself.
A review that stops at page one under-reports.
actingUserId is the account ID. Passing a member id returns
nothing, which looks like "no activity".
- Long ranges are slow and large. A year of events for a busy
organization is many pages and invites rate limiting. Narrow the window
or filter by user or item.
- Personal data. Events carry emails (once resolved), IP addresses and
device details. Keep them inside the ticket or report that needs them.
Related Skills
1---2name: bitwarden-event-log-review3description: >4 Reading a client's Bitwarden organization event log through the5 admin-gated bitwarden_events_list tool: date ranges and the 367-day limit,6 continuationToken paging, the one-filter rule, the event types that matter7 to an MSP (failed logins, 2FA changes, vault exports, item views and8 copies, member and policy changes), resolving IDs back to members, groups9 and collections, and handling the personal data events carry.10when_to_use: >-11 When investigating what happened in a client's Bitwarden organization or12 running a periodic activity review. Use when: bitwarden event log,13 bitwarden audit log, who exported the vault, failed bitwarden logins, who14 changed a bitwarden policy, who disabled 2fa, bitwarden suspicious15 activity, or who viewed this item.16metadata:17 source: https://skillmd.com/skills/wyre-ai/bitwarden-event-log-review18---1920# Bitwarden Event Log Review2122## Overview2324The event log is the organization's audit trail: logins, item access,25member and policy changes. It is the only place the Public API shows what26people *did*, as opposed to what they are allowed to do.2728**`bitwarden_events_list` is admin-gated in Conduit.** It needs the admin29tier in the gateway access editor. If the call is denied, say that the event30review could not run; do not substitute guesses from the other tools. The31lookups this skill uses to put names to IDs are read tier:32`bitwarden_members_list`, `bitwarden_members_get`, `bitwarden_groups_get`,33`bitwarden_collections_get` and `bitwarden_policies_list`.3435## Anti-triggers3637- **One leaver's full access picture** — use38 [offboarding-access-review](../offboarding-access-review/SKILL.md); it39 calls the event log as one step.40- **Current policy settings** — use41 [security-posture](../security-posture/SKILL.md); the log shows changes,42 not the current state.4344## Key Concepts4546### Request shape4748| Parameter | Use |49|---|---|50| `start`, `end` | ISO 8601 range. Default is the last 30 days. Over 367 days is rejected. |51| `actingUserId` | Events performed by one Bitwarden account (the member's `userId`, not their member `id`) |52| `itemId` | Events about one vault item |53| `secretId`, `projectId` | Events about one Secrets Manager secret or project |54| `continuationToken` | The token from the previous page, passed back unchanged |5556Only one of `actingUserId`, `itemId`, `secretId`, `projectId` per call.5758### What an event carries5960Each event has a numeric `type`, a `date`, and, depending on the type,61IDs such as `actingUserId`, `memberId`, `itemId`, `collectionId`, `groupId`62or `policyId`, plus `ipAddress` and a numeric `device` client type. There63are no names: resolve IDs with the read tools (members by `userId` or `id`,64groups and collections by ID). Vault item names are encrypted and cannot be65resolved; report the `itemId`.6667### Event types worth watching6869| Type | Event | Why it matters |70|---|---|---|71| 1000 | User logged in | Baseline; unusual IPs or times stand out |72| 1002 / 1003 | User updated / disabled two-step login | 1003 on an owner or admin is urgent |73| 1005 / 1006 | Failed login / failed two-step login | Clusters suggest password spraying or a stolen master password |74| 1007 | User exported their vault | Possible data exfiltration |75| 1107 | Item viewed | Who looked at a credential |76| 1108 | Item password viewed | Stronger signal than 1107 |77| 1111 | Item password copied | The value left the vault UI |78| 1500 / 1501 | Member invited / confirmed | Who added whom |79| 1503 | Member removed | Offboarding evidence |80| 1511 / 1512 | Member revoked / restored | A restore after a revoke deserves a reason |81| 1600 | Organization settings edited | Confirm the change was expected |82| 1602 | Organization vault exported | Everything shared may have left |83| 1700 | Policy edited | Resolve `policyId` against `bitwarden_policies_list` |8485These codes follow Bitwarden's event list. Check the full catalogue on86Bitwarden's [event logs page](https://bitwarden.com/help/event-logs/) before87you rely on a type that is not in this table.8889## Common Workflows9091### Periodic activity review (monthly)92931. Call `bitwarden_events_list` with `start` and `end` covering the month.94 Page with `continuationToken` until it is `null`.952. If a page comes back `truncated`, do not page on (that skips the dropped96 events); re-run that stretch with a shorter window.973. Group events by type. Report counts for the watch-list types, and list98 every 1003, 1007, 1602 and 1700 event individually with the acting99 member resolved by name.1004. Look for failed-login clusters (1005, 1006): same account many times, or101 many accounts from one IP.102103### Answering "who did X?"104105- **Who changed a policy?** Range around the change, filter nothing, keep106 type 1700 events, resolve `actingUserId` to a member.107- **Who touched this item?** Use `itemId` with a range covering the period108 of interest; keep 1107, 1108, 1111.109- **What did this person do?** Use `actingUserId` (their `userId`).110111### Output112113Lead with any urgent events (2FA disabled on an admin, vault exports, policy114changes nobody expected). Then a counts table by type, then the detail. Put115IP addresses and device details in the technical appendix, not the summary.116117## Gotchas118119- **Paging is manual.** The tool never follows `continuationToken` itself.120 A review that stops at page one under-reports.121- **`actingUserId` is the account ID.** Passing a member `id` returns122 nothing, which looks like "no activity".123- **Long ranges are slow and large.** A year of events for a busy124 organization is many pages and invites rate limiting. Narrow the window125 or filter by user or item.126- **Personal data.** Events carry emails (once resolved), IP addresses and127 device details. Keep them inside the ticket or report that needs them.128129## Related Skills130131- [api-patterns](../api-patterns/SKILL.md) - errors, rate limits, truncation132- [offboarding-access-review](../offboarding-access-review/SKILL.md) - per-user access and activity133- [security-posture](../security-posture/SKILL.md) - current policy state