Bitwarden License Reconciliation
Overview
MSPs resell or manage Bitwarden seats and bill clients for them. Drift
creeps in from both sides: invites that were never accepted, leavers who
were revoked but not removed, and autoscale quietly adding seats. This skill
compares bitwarden_subscription_get with bitwarden_members_list and
produces numbers the MSP can check against its own agreement or invoice.
Both tools are read tier in Conduit; no admin grant is needed. The plugin
cannot change seats or autoscale limits; an owner does that in the Admin
Console under Billing > Subscription.
Key Concepts
bitwarden_subscription_get returns:
- Password Manager: purchased seats, the maximum autoscale seats, and
storage.
- Secrets Manager (if the organization has it): seats and service
accounts, with their own autoscale limits.
An autoscale limit that is empty or null means Bitwarden may keep adding
seats as members join. That is the usual source of a surprise invoice.
bitwarden_members_list gives each member's status: Revoked (-1),
Invited (0), Accepted (1), Confirmed (2), Staged (3). Which of these occupy
a paid seat is Bitwarden's rule, not this plugin's: the occupied-seat figure
on the Admin Console billing page is the authority. Report the counts by
status and let that page settle the arithmetic.
Common Workflows
Seat reconciliation for one client
- Call
bitwarden_subscription_get. Record Password Manager seats and the
autoscale limit; record Secrets Manager seats and service accounts if
present.
- Call
bitwarden_members_list. If the response is truncated, stop and
report that the member count is partial; a seat reconciliation on a cut
list is wrong by definition.
- Count members by
status.
- Flag:
- Headroom: purchased seats minus members. Large headroom is paid
but unused.
- Autoscale exposure: no autoscale limit, or a limit far above the
purchased seats.
- Stale invites: Invited and Accepted members. Each is either a
person who never finished onboarding or a seat held for no one.
- Revoked members: offboarded people still listed. Confirm with the
client whether they should be removed.
- Compare the purchased seats with the quantity on the MSP's billing
agreement for this client (from the PSA or distributor plugin, if one is
connected) and note any mismatch.
Output
A small table: purchased seats, autoscale limit, members by status, and the
agreement quantity if known. Then a list of actions, each for a person:
remove these revoked members, chase or cancel these invites, set an
autoscale limit, adjust the agreement.
Gotchas
- Service accounts are Secrets Manager machine identities, billed
separately from people. Do not add them to the Password Manager seat
comparison.
- Seats change between calls. A member who joins mid-review can make the
numbers disagree by one. Re-run both calls together if the totals look
off by a small amount.
- Email is not a unique person. A contractor with two addresses holds two
seats; look for near-duplicate emails before declaring the count right.
Related Skills
1---2name: bitwarden-license-reconciliation3description: >4 Reconciling a client's Bitwarden subscription against its real membership:5 Password Manager and Secrets Manager seats and autoscale limits from the6 subscription, member counts by status, invites that never completed,7 revoked members still listed, and the figures to check against the MSP's8 billing agreement. Read-only; seat changes happen in the Admin Console.9when_to_use: >-10 When checking whether a client is paying for the right number of Bitwarden11 seats, preparing a renewal or true-up, or explaining an autoscale charge.12 Use when: bitwarden seats, bitwarden license count, bitwarden billing,13 bitwarden subscription, autoscale seats, unused bitwarden seats, or14 bitwarden true-up.15metadata:16 source: https://skillmd.com/skills/wyre-ai/bitwarden-license-reconciliation17---1819# Bitwarden License Reconciliation2021## Overview2223MSPs resell or manage Bitwarden seats and bill clients for them. Drift24creeps in from both sides: invites that were never accepted, leavers who25were revoked but not removed, and autoscale quietly adding seats. This skill26compares `bitwarden_subscription_get` with `bitwarden_members_list` and27produces numbers the MSP can check against its own agreement or invoice.2829Both tools are read tier in Conduit; no admin grant is needed. The plugin30cannot change seats or autoscale limits; an owner does that in the Admin31Console under Billing > Subscription.3233## Key Concepts3435`bitwarden_subscription_get` returns:3637- **Password Manager**: purchased seats, the maximum autoscale seats, and38 storage.39- **Secrets Manager** (if the organization has it): seats and service40 accounts, with their own autoscale limits.4142An autoscale limit that is empty or null means Bitwarden may keep adding43seats as members join. That is the usual source of a surprise invoice.4445`bitwarden_members_list` gives each member's `status`: Revoked (-1),46Invited (0), Accepted (1), Confirmed (2), Staged (3). Which of these occupy47a paid seat is Bitwarden's rule, not this plugin's: the occupied-seat figure48on the Admin Console billing page is the authority. Report the counts by49status and let that page settle the arithmetic.5051## Common Workflows5253### Seat reconciliation for one client54551. Call `bitwarden_subscription_get`. Record Password Manager seats and the56 autoscale limit; record Secrets Manager seats and service accounts if57 present.582. Call `bitwarden_members_list`. If the response is `truncated`, stop and59 report that the member count is partial; a seat reconciliation on a cut60 list is wrong by definition.613. Count members by `status`.624. Flag:63 - **Headroom**: purchased seats minus members. Large headroom is paid64 but unused.65 - **Autoscale exposure**: no autoscale limit, or a limit far above the66 purchased seats.67 - **Stale invites**: Invited and Accepted members. Each is either a68 person who never finished onboarding or a seat held for no one.69 - **Revoked members**: offboarded people still listed. Confirm with the70 client whether they should be removed.715. Compare the purchased seats with the quantity on the MSP's billing72 agreement for this client (from the PSA or distributor plugin, if one is73 connected) and note any mismatch.7475### Output7677A small table: purchased seats, autoscale limit, members by status, and the78agreement quantity if known. Then a list of actions, each for a person:79remove these revoked members, chase or cancel these invites, set an80autoscale limit, adjust the agreement.8182## Gotchas8384- **Service accounts are Secrets Manager machine identities**, billed85 separately from people. Do not add them to the Password Manager seat86 comparison.87- **Seats change between calls.** A member who joins mid-review can make the88 numbers disagree by one. Re-run both calls together if the totals look89 off by a small amount.90- **Email is not a unique person.** A contractor with two addresses holds two91 seats; look for near-duplicate emails before declaring the count right.9293## Related Skills9495- [api-patterns](../api-patterns/SKILL.md) - member status enum and truncation96- [offboarding-access-review](../offboarding-access-review/SKILL.md) - before removing a revoked member, check what they could reach