Skip to content

Bitwarden ​

Counts seats per Bitwarden organization via the Bitwarden Public API.

Setup ​

  1. In the Bitwarden admin console, generate the API key (client_id + client_secret) for each customer organization.
  2. In the Bitwarden view, use the gear icon to create one entry per organization: customer name + API key.

The keys are stored write-only — no longer viewable after creation, only replaceable or deletable.

Metrics ​

MetricCount
seatsoccupied seats of the organization

Splitting one organization across several customers ​

Some customers share one Bitwarden organization with their sister companies; the members differ only in the domain of their e-mail address. Multiverse can split such an organization by domain. No extra access is needed — the stored API key already lists the organization's members:

  1. In Multiverse → Bitwarden → API keys click Split… in the key's row. The dialog reads the members with the key and shows how many occupy a seat (invited, accepted and confirmed members do; revoked and staged members are left out), how many carry an e-mail address, and the members per e-mail domain. Reload reads them again.
  2. Add a domain rule per domain that belongs to another customer (Assign… in the domain table prefills it): domain → customer. Domains without a rule, and members without an e-mail address, stay with the key's own customer. Several domains may point to the same customer (they form one part); a rule naming the key's own customer is the same as no rule.

From the next snapshot on the key's seats appear under several customers: the key's own customer plus one per rule customer. Bitwarden reports the seats per organization, not per member, so they are split in proportion to the member numbers per domain, rounded to whole seats with the largest remainder; the parts always add up to the organization's seats. The dialog previews that split under Next snapshot. A customer that also has a key of its own, or receives seats from several split keys, shows one row with the sum — the customer name is the identity in Bitwarden.

A member list that fails (the self-hosted server is down, typically) no longer leaves every seat with the key's customer: the snapshot spreads today's seats by the members of the last successful read, so the customers of the rules keep their share (only a key whose members were never read stays whole); the snapshot carries a warning naming the day of that read, which the invoice runs repeat. A key that fails entirely leaves out every customer it feeds (its own and its rules') in that snapshot, so no customer shows a partial sum — these customers are recorded as not read and keep the seats of their last snapshot, while a customer whose key was deleted is gone at once. A subscription that reports no seat count fails the key instead of billing 0 seats. The Bitwarden view names the failing key; the key list marks split keys with "N domain rules".

Self-hosted instances ​

Some licences run a self-hosted Bitwarden: the provider's cloud organization carries the seats, but its member list holds nobody except the provider's owner — the users live on the customer's own server. Give the key a members source in the split dialog: the server URL of the self-hosted instance (just the host, such as https://vault.example.com; a pasted /api or /identity suffix is dropped) and the organization API key of the organization on that instance (its admin console: Settings → Organization info → API key). From then on the dialog, the live view and the snapshot read the members from the instance while the seats keep coming from the cloud key; the key list marks such keys "self-hosted". Remove the source and the cloud organization's own members are used again.

Export of the licensed users ​

Licensed users (CSV) in the Bitwarden view's toolbar exports the members of every API key that occupy a seat — invited, accepted or confirmed, the members the seats count — as a CSV file, read live from each key's member source (the cloud organization or the self-hosted instance): organization (the key's customer), e-mail, name, status, Counts towards — the customer a member's seat is billed to under the key's domain rules (without rules: the key's own customer) — and the member source. The customer filter of the export dialog works on Counts towards. A key whose members cannot be read is named in the dialog; its members are missing from that export.

Specifics ​

  • The customer of a domain rule counts as a customer source like the key's customer does (listed in the customer view before the first snapshot, renamed along with merges).
  • The customer name on the API key is the customer identity — it counts as a customer source in the customer view (even before the first snapshot) and is automatically renamed along with merges.