1Password Offboarding Review
Overview
When someone leaves a client, the MSP has to answer three questions: is their 1Password
seat closed, did they touch anything after they left, and which shared credentials did they
use that should now be rotated. The Events API answers the last two; the Users API answers
the first. This plugin is read-only, so the output is a findings report plus a list of
console actions for a technician or the client's 1Password owner.
Tools used
| Tool |
Purpose |
Conduit tier |
1password_users_list |
Find the user and their state |
read |
1password_users_get |
Re-check one user's state |
read |
1password_item_usages_list |
Shared-vault items they used |
admin |
1password_signin_attempts_list |
Sign-ins around and after departure |
admin |
1password_audit_events_list |
Who suspended them; changes they made before leaving |
admin |
1password_events_introspect |
Confirm the account and which feeds the token can read |
read |
The three Events feeds are admin-gated in Conduit. Without the admin tier the review is
limited to seat state; say so in the report.
Inputs to collect
- The user's email address at the client.
- The departure date and time (with time zone). If only a date is known, use the start of
that day in the client's time zone.
- How far back to look for item usage. Default: 30 days before departure. Events are kept
for 120 days, so a departure older than that cannot be reviewed for activity.
Workflow
- Confirm the account. Call
1password_events_introspect. Check the account_uuid is
the client you expect and note which of auditevents, itemusages and signinattempts
the token has. Skip the steps for missing features and record them as gaps.
- Find the user. Page
1password_users_list (no filter) until you find the email.
Record the user ID, state and create_time. If the email is not there, the user may
have been deleted rather than suspended; note it and continue with the Events feeds,
matching on email.
- Seat state.
ACTIVE after the departure date is the first finding: the account is
still open. SUSPENDED is expected.
- Post-departure sign-ins. Page
1password_signin_attempts_list with start_time at
the departure time. Keep attempts whose target user matches the email. A successful
sign-in after departure is a critical finding; failed attempts are worth listing (someone
is still trying the account).
- Item usage. Page
1password_item_usages_list from the look-back start to now. Keep
events whose user matches. Build the distinct set of vault UUID + item UUID pairs, with
the last time and the actions seen for each. Any usage after the departure time is a
critical finding.
- Audit trail. Page
1password_audit_events_list over the same window. Keep events
where the user is the actor (changes they made: group membership, vault sharing, invites)
or the object (who suspended or removed them, and when).
- Report (format below).
The Events feeds have no user filter. Every step pages the whole window and filters
locally, so keep windows tight on large accounts and state the page budget if you stop
early.
Matching users across the APIs
Match on email. The Users API returns email; the Events feeds carry the user's email
alongside a UUID. UUIDs usually line up with the Users API ID, but email is the field both
APIs show reliably. Watch for aliases and renamed addresses: if the client renamed the
user's email at departure, ask for the old address too.
Report format
- Summary line: seat state, last successful sign-in, last item usage, and whether any
activity happened after departure.
- Critical findings: post-departure sign-ins or item usage, an
ACTIVE seat.
- Credentials to rotate: table of vault UUID, item UUID, last used, actions. These are
the shared items the user handled in the window. The technician maps UUIDs to names in
the 1Password console.
- Changes they made before leaving: audit events with the user as actor.
- Coverage gaps: feeds the token lacks, the Conduit admin tier missing, a window that
reaches past 120 days, or a page budget that cut the review short.
- Console actions (manual, outside this plugin): suspend or delete the user, remove
them from groups, move any private vault they shared, rotate the listed items, recover
the account if needed.
Gotchas
- Private vault use is not in the feed. Item usage covers shared vaults. Personal or
private vault activity does not appear, so "no item usage" does not mean "used nothing".
- Suspended is not deleted. A suspended user keeps their account and private vault.
Flag long-suspended users so the client can decide whether to delete them.
- No names for items. Do not guess item names from UUIDs.
- This plugin cannot suspend. Never tell the user the seat was closed; hand back the
console action.
1---2name: "1password-offboarding-review"3description: >4 How to review a departing or departed user's 1Password footprint with the5 read-only tools: confirm the seat is suspended, find every shared-vault item6 they used so the client can rotate it, catch sign-ins or item access after the7 departure date, and see who suspended them and when. Covers matching users8 across the Events and Users APIs, choosing the time window, and the manual9 console steps the report must hand back, since nothing here can suspend or10 revoke.11when_to_use: >-12 When an employee at a client is leaving or has left and the MSP needs to know what they could13 reach in 1Password and what must be rotated. Use when: 1password offboarding, departed user14 1password, terminated employee password manager, which passwords to rotate, ex-employee vault15 access, or leaver review 1password.16metadata:17 source: https://skillmd.com/skills/wyre-ai/1password-offboarding-review18---1920# 1Password Offboarding Review2122## Overview2324When someone leaves a client, the MSP has to answer three questions: is their 1Password25seat closed, did they touch anything after they left, and which shared credentials did they26use that should now be rotated. The Events API answers the last two; the Users API answers27the first. This plugin is read-only, so the output is a findings report plus a list of28console actions for a technician or the client's 1Password owner.2930## Tools used3132| Tool | Purpose | Conduit tier |33|---|---|---|34| `1password_users_list` | Find the user and their state | read |35| `1password_users_get` | Re-check one user's state | read |36| `1password_item_usages_list` | Shared-vault items they used | admin |37| `1password_signin_attempts_list` | Sign-ins around and after departure | admin |38| `1password_audit_events_list` | Who suspended them; changes they made before leaving | admin |39| `1password_events_introspect` | Confirm the account and which feeds the token can read | read |4041The three Events feeds are admin-gated in Conduit. Without the admin tier the review is42limited to seat state; say so in the report.4344## Inputs to collect4546- The user's email address at the client.47- The departure date and time (with time zone). If only a date is known, use the start of48 that day in the client's time zone.49- How far back to look for item usage. Default: 30 days before departure. Events are kept50 for 120 days, so a departure older than that cannot be reviewed for activity.5152## Workflow53541. **Confirm the account.** Call `1password_events_introspect`. Check the `account_uuid` is55 the client you expect and note which of `auditevents`, `itemusages` and `signinattempts`56 the token has. Skip the steps for missing features and record them as gaps.572. **Find the user.** Page `1password_users_list` (no filter) until you find the email.58 Record the user ID, `state` and `create_time`. If the email is not there, the user may59 have been deleted rather than suspended; note it and continue with the Events feeds,60 matching on email.613. **Seat state.** `ACTIVE` after the departure date is the first finding: the account is62 still open. `SUSPENDED` is expected.634. **Post-departure sign-ins.** Page `1password_signin_attempts_list` with `start_time` at64 the departure time. Keep attempts whose target user matches the email. A successful65 sign-in after departure is a critical finding; failed attempts are worth listing (someone66 is still trying the account).675. **Item usage.** Page `1password_item_usages_list` from the look-back start to now. Keep68 events whose user matches. Build the distinct set of vault UUID + item UUID pairs, with69 the last time and the actions seen for each. Any usage after the departure time is a70 critical finding.716. **Audit trail.** Page `1password_audit_events_list` over the same window. Keep events72 where the user is the actor (changes they made: group membership, vault sharing, invites)73 or the object (who suspended or removed them, and when).747. **Report** (format below).7576The Events feeds have no user filter. Every step pages the whole window and filters77locally, so keep windows tight on large accounts and state the page budget if you stop78early.7980## Matching users across the APIs8182Match on email. The Users API returns `email`; the Events feeds carry the user's email83alongside a UUID. UUIDs usually line up with the Users API ID, but email is the field both84APIs show reliably. Watch for aliases and renamed addresses: if the client renamed the85user's email at departure, ask for the old address too.8687## Report format88891. **Summary line**: seat state, last successful sign-in, last item usage, and whether any90 activity happened after departure.912. **Critical findings**: post-departure sign-ins or item usage, an `ACTIVE` seat.923. **Credentials to rotate**: table of vault UUID, item UUID, last used, actions. These are93 the shared items the user handled in the window. The technician maps UUIDs to names in94 the 1Password console.954. **Changes they made before leaving**: audit events with the user as actor.965. **Coverage gaps**: feeds the token lacks, the Conduit admin tier missing, a window that97 reaches past 120 days, or a page budget that cut the review short.986. **Console actions** (manual, outside this plugin): suspend or delete the user, remove99 them from groups, move any private vault they shared, rotate the listed items, recover100 the account if needed.101102## Gotchas103104- **Private vault use is not in the feed.** Item usage covers shared vaults. Personal or105 private vault activity does not appear, so "no item usage" does not mean "used nothing".106- **Suspended is not deleted.** A suspended user keeps their account and private vault.107 Flag long-suspended users so the client can decide whether to delete them.108- **No names for items.** Do not guess item names from UUIDs.109- **This plugin cannot suspend.** Never tell the user the seat was closed; hand back the110 console action.