1Password Account Hygiene
Overview
Two things drift in a client's 1Password account between reviews: the user list (people
leave, are suspended and never removed, or were invited and never signed in) and access
(groups and vaults gain members). This skill produces a seat reconciliation and a change log
for the period. It reads only; every fix is a console action.
Tools used
| Tool |
Purpose |
Conduit tier |
1password_users_list |
Full seat inventory with state and create time |
read |
1password_users_get |
Detail on one user |
read |
1password_events_introspect |
Confirm the account and available feeds |
read |
1password_audit_events_list |
Admin and membership changes over the period |
admin |
1password_signin_attempts_list |
Optional: last successful sign-in per user, within 120 days |
admin |
With only the read tier, deliver the seat reconciliation and say the change log needs the
Conduit admin tier.
Workflow
1. Seat inventory
Page 1password_users_list with max_page_size 500 until next_page_token is absent.
Count ACTIVE and SUSPENDED. Keep email, display name, state and create_time per user.
2. Reconcile against headcount
Ask for, or pull from another connected system, the client's current staff list (for
example the M365 licensed users or the PSA contact list). Then classify:
| Finding |
Meaning |
Suggested action |
ACTIVE, not on the staff list |
Possible leaver with an open account |
Run the offboarding review |
SUSPENDED for a long time |
Account kept but unused |
Client decides whether to delete |
| On the staff list, no 1Password user |
Not onboarded, or using a personal vault |
Confirm with the client |
| Shared or generic mailbox as a user |
Shared login, weak accountability |
Recommend named users |
3. Activity check (optional, admin tier)
Page 1password_signin_attempts_list from 90 days ago, keep success attempts, and record
each user's latest. ACTIVE users with no successful sign-in in 90 days are candidates for
review. The feed only reaches back 120 days, so "never" means "not in 120 days".
4. Change log (admin tier)
Page 1password_audit_events_list from the start of the review period. Group events by
action and object type, and list who did what. Pay attention to:
- invitations and new users;
- users added to or removed from groups, especially administrative groups;
- vault access granted or removed;
- account-level setting and policy changes;
- suspensions, reactivations and deletions.
Use the action and object-type values the feed returns; do not rename them into categories
the data does not support. List the actor for each change so the client can confirm it was
expected.
5. Report
- Seats: active, suspended, total; change since the last review if known.
- Reconciliation table: users in each finding category above.
- Inactive accounts:
ACTIVE with no recent successful sign-in.
- Change log: grouped by type, with actor and time.
- Console actions (manual): delete or suspend, remove from groups, review admin
membership, confirm settings changes.
- Gaps: missing feeds, missing admin tier, period longer than 120 days.
Gotchas
- Seats are not billing. The Users API reports users and state, not the client's
subscription size or invoice. Compare with the 1Password billing page before a renewal.
- Policies are not readable. No tool returns current MFA, password or firewall policy.
Only changes made inside the window show up, as audit events.
- Retention. A quarterly review fits inside 120 days; anything longer does not.
- Large accounts. Audit feeds on big accounts run to many pages. Keep
limit at a few
hundred and state the page budget if you stop.
1---2name: "1password-account-hygiene"3description: >4 Periodic hygiene review of a client's 1Password account for QBRs and license5 true-ups: reconciling active and suspended seats against the client's6 headcount, finding long-suspended and never-used seats, and summarising the7 admin changes made during the review period (who was invited, who gained or8 lost group and vault access, who changed account settings). Seat inventory9 uses read-tier tools; the change summary uses the admin-gated audit feed.10when_to_use: >-11 When an MSP prepares a quarterly or monthly review of a client's 1Password account, checks12 seat counts before a renewal, or wants to know what admins changed. Use when: 1password seat13 audit, 1password license count, 1password qbr, 1password admin changes, who changed 1password,14 or password manager user review.15metadata:16 source: https://skillmd.com/skills/wyre-ai/1password-account-hygiene17---1819# 1Password Account Hygiene2021## Overview2223Two things drift in a client's 1Password account between reviews: the user list (people24leave, are suspended and never removed, or were invited and never signed in) and access25(groups and vaults gain members). This skill produces a seat reconciliation and a change log26for the period. It reads only; every fix is a console action.2728## Tools used2930| Tool | Purpose | Conduit tier |31|---|---|---|32| `1password_users_list` | Full seat inventory with state and create time | read |33| `1password_users_get` | Detail on one user | read |34| `1password_events_introspect` | Confirm the account and available feeds | read |35| `1password_audit_events_list` | Admin and membership changes over the period | admin |36| `1password_signin_attempts_list` | Optional: last successful sign-in per user, within 120 days | admin |3738With only the read tier, deliver the seat reconciliation and say the change log needs the39Conduit admin tier.4041## Workflow4243### 1. Seat inventory4445Page `1password_users_list` with `max_page_size` 500 until `next_page_token` is absent.46Count `ACTIVE` and `SUSPENDED`. Keep email, display name, state and `create_time` per user.4748### 2. Reconcile against headcount4950Ask for, or pull from another connected system, the client's current staff list (for51example the M365 licensed users or the PSA contact list). Then classify:5253| Finding | Meaning | Suggested action |54|---|---|---|55| `ACTIVE`, not on the staff list | Possible leaver with an open account | Run the offboarding review |56| `SUSPENDED` for a long time | Account kept but unused | Client decides whether to delete |57| On the staff list, no 1Password user | Not onboarded, or using a personal vault | Confirm with the client |58| Shared or generic mailbox as a user | Shared login, weak accountability | Recommend named users |5960### 3. Activity check (optional, admin tier)6162Page `1password_signin_attempts_list` from 90 days ago, keep `success` attempts, and record63each user's latest. `ACTIVE` users with no successful sign-in in 90 days are candidates for64review. The feed only reaches back 120 days, so "never" means "not in 120 days".6566### 4. Change log (admin tier)6768Page `1password_audit_events_list` from the start of the review period. Group events by69action and object type, and list who did what. Pay attention to:7071- invitations and new users;72- users added to or removed from groups, especially administrative groups;73- vault access granted or removed;74- account-level setting and policy changes;75- suspensions, reactivations and deletions.7677Use the action and object-type values the feed returns; do not rename them into categories78the data does not support. List the actor for each change so the client can confirm it was79expected.8081### 5. Report82831. **Seats**: active, suspended, total; change since the last review if known.842. **Reconciliation table**: users in each finding category above.853. **Inactive accounts**: `ACTIVE` with no recent successful sign-in.864. **Change log**: grouped by type, with actor and time.875. **Console actions** (manual): delete or suspend, remove from groups, review admin88 membership, confirm settings changes.896. **Gaps**: missing feeds, missing admin tier, period longer than 120 days.9091## Gotchas9293- **Seats are not billing.** The Users API reports users and state, not the client's94 subscription size or invoice. Compare with the 1Password billing page before a renewal.95- **Policies are not readable.** No tool returns current MFA, password or firewall policy.96 Only changes made inside the window show up, as audit events.97- **Retention.** A quarterly review fits inside 120 days; anything longer does not.98- **Large accounts.** Audit feeds on big accounts run to many pages. Keep `limit` at a few99 hundred and state the page budget if you stop.