* [PM-43274] feat: Add Privileged Controls plan pricing and billing flag * [PM-43274] feat: Add Privileged Controls purchase call to the organization billing client * [PM-43274] feat: Add the Privileged Controls purchase component * [PM-43274] feat: Show the Privileged Controls purchase on the subscription page * [PM-43274] fix: Skip the Privileged Controls purchase when seats are empty * [PM-43274] fix: Validate the Privileged Controls purchase form before submitting * [PM-43274] feat: Add the Privileged Controls product logo The Privileged Controls purchase block needs header art matching the Secrets Manager purchase block. This mirrors SecretsManagerAlt with the product name outlined in DM Sans, the brand font used by the Secrets Manager artwork. * [PM-43274] feat: Polish the Privileged Controls purchase block - Show the logo and feature copy in place of the placeholders - Show the More from Bitwarden heading once when the Secrets Manager purchase is also on the page - Show the max potential seat cost under the seat limit, as Password Manager does - Require the seat limit to be a whole number above the seat count so it is a limit the organization can autoscale up to * [PM-43274] fix: Reject decimal Privileged Controls seat counts Seats are bought in whole units, but the seat count field accepted values like 10.5. * [PM-43274] feat: Cap Privileged Controls seats at Password Manager seats Privileged Controls no longer has a seat minimum. An organization can buy from 1 seat up to its Password Manager seat count, and its Privileged Controls seat limit can't exceed its Password Manager seat limit, or its Password Manager seat count when it has no limit. - Remove the seat minimum validation, its hint, and the unused defaultSeatMinimum plan field - Default seats to 1 * [PM-43274] fix: Hide the Privileged Controls purchase when the server reports it The purchase block checked usePam on the locally synced organization, which stays stale until the client syncs. An organization that got Privileged Controls in another session still saw the purchase offer. Read usePam from the subscription response instead, which the page fetches fresh on load. * [PM-43274] refactor: Simplify the Privileged Controls purchase form Keeps every seat check on the field that displays it, so errors show under the right input without a parent lookup, and drops the enable/disable toggling that the template's @if already covers. Also hides the purchase for provider organizations, matching the Secrets Manager subscribe gate. * [PM-43274] feat: Update Secrets Manager and Privileged Controls purchase copy Match the updated design copy for the More from Bitwarden cards. Secrets Manager gets new keys because its existing strings are already translated. * [PM-43274] fix: Add a space between the slash and interval in purchase prices * [PM-43274] feat: Hide the Privileged Controls seat limit behind a limit checkbox Match the Password Manager seat limit pattern so the seat limit is opt-in. Unchecking the limit clears it so no hidden value is submitted. * [PM-43274] feat: Apply final Secrets Manager and Privileged Controls copy Design finalized the More from Bitwarden copy. Privileged Controls gets the new description and feature list. Secrets Manager gets a new description key, since the old string is already translated. * [PM-43274] fix: Use semantic color tokens in the purchase blocks for dark mode The legacy muted text and secondary border tokens don't match the design in dark mode. Use fg-body, fg-heading, and border-base, as the design specifies. * [PM-43274] feat: Drop "included" from the Secrets Manager machine accounts bullet Match the final design copy. Reuse the existing includedMachineAccountsV2 key, which already reads "$COUNT$ machine accounts", and remove the now-unused machineAccountsIncluded key. * [PM-43274] feat: Show the Secrets Manager and Privileged Controls purchase blocks as accordions Design asked for each purchase block's header to be an accordion header. Use the design system accordion's default variant as is, open by default. The accordion title replaces the header art and in-block title, so remove the now-unused plan name title code and its strings. The Secrets Manager block is shared, so the organization plans page and the legacy subscription page also show the accordion. * [PM-43274] chore: Remove the unused Secrets Manager and Privileged Controls header art The purchase blocks now use accordion headers, so nothing references these SVGs anymore. * [PM-43274] feat: Update the Privileged Controls seat limit hint copy Design asked for the hint to say members can't be given access to Privileged Controls once the limit is reached. * [PM-43274] fix: Add spacing between the purchase block feature bullets Design flagged the bullet list as too tight. Add 8px between items, as the design specifies. * [PM-43274] chore: Remove the unused subscribeToSecretsManager string The Secrets Manager purchase checkbox now reads addSecretsManager, so nothing reads this key. * [PM-43274] test: Fold the Privileged Controls plan parsing assertions into one test The new test duplicated "parses PrivilegedControls when present", so its seat plan ID and base seats assertions move there.
Bitwarden Client Applications
This repository houses all Bitwarden client applications except the mobile applications (iOS | android).
Please refer to the Clients section of the Contributing Documentation for build instructions, recommended tooling, code style tips, and lots of other great information to get you started.
Related projects:
- bitwarden/server: The core infrastructure backend (API, database, Docker, etc).
- bitwarden/ios: Bitwarden iOS Password Manager & Authenticator apps.
- bitwarden/android: Bitwarden Android Password Manager & Authenticator apps.
- bitwarden/directory-connector: A tool for syncing a directory (AD, LDAP, Azure, G Suite, Okta) to an organization.
We're Hiring!
Interested in contributing in a big way? Consider joining our team! We're hiring for many positions. Please take a look at our Careers page to see what opportunities are currently open as well as what it's like to work at Bitwarden.
Contribute
Code contributions are welcome! Please commit any pull requests against the main branch. Learn more about how to contribute by reading the Contributing Guidelines. Check out the Contributing Documentation for how to get started with your first contribution.
Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md file.
