Consumers project a bit-berry, which the avatar sizes and places at the top end corner. The
avatar is masked around it instead of drawing a ring, so the gap works on any background.
* [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.
`bw update` picked the first release zip whose URL contained `bw-<os>`.
It ignored which build was running and the CPU architecture, so OSS users
were sent the commercial build and arm64 users were sent the x64 build.
- Add `licenseType` to the CLI ServiceContainer ("oss"), overridden to
"bit" in the Bitwarden-licensed container, and pass it to UpdateCommand.
- Build the exact asset name, bw-{license}-{os}[-arm64]-{version}.zip,
from the license, process.platform, process.arch and the release tag,
and match it against asset names.
- Fall back to the release page when no matching asset exists or the
OS/architecture has no published build.
- Type the GitHub release response and remove @ts-strict-ignore.
Depends on the bw-bit-* asset rename (BRE-2408).
Commercial CLI zips were unprefixed (bw-linux-*, bw-macos-*, bw-windows-*)
while OSS zips use bw-oss-*. Set the commercial artifact_prefix to -bit so
both license types follow bw-{license}-{os}[-arm64]-{version}.zip, and point
the snap job and snapcraft.yaml at bw-bit-linux-*.
* Vault: show restricted ciphers in the browser popup
The popup lists restricted (partial) ciphers and swaps in a cipher's
revealed view while one exists. The edit, clone and assign-collections
routes send a blocked restricted cipher back to its view, and the view
page, more-options menu, copy actions, password history and add-edit
respect the restricted-cipher rule.
A host can provide VAULT_ROW_ACCESS for each row's access status and
overflow actions, and contribute list table filters with coloured tiles.
Unprovided, rows show no status and the popup behaves as before.
* Vault: replace the popup's row access seam with neutral slots
Addresses review feedback on #24596.
- Replace VAULT_ROW_ACCESS with VAULT_ROW_ICON (a component slot) and
VAULT_ROW_SUBTITLE (a text provider). item-more-options renders
VAULT_ROW_ACTIONS after View, checked against its own built-in IDs.
- Add an optional `disabled` to row actions, honoured by web's menu too,
and export the contributed action ID check from CipherRowMenuService.
- Drop accessActive from the more-options menu, so edit under a live
reveal follows the restricted-cipher policy. Clone checks the policy.
- Name the list table's contributed filter generically, key it by the
provider's `key`, and persist selections as contributedFilterIds.
- Move gating into the row actions (showCopyActions) and launchCipher,
and drop the separate revealed-ID stream: the list already swaps
revealed views in for their restricted rows.
- Lift the view footer's edit and restore conditions into the component.
- Drop the five browser strings, which Vault no longer uses.
Extracts FillCipherPolicy from pam/uat. Autofill reads ciphers only
through the policy with a CipherUse. The OSS DefaultFillCipherPolicy
wraps CipherService and changes no behaviour; a commercial build can
supply its own through MainBackground's new overrides argument.
Every user-started fill, the save prompt, the badge, the context menu
and the inline menu go through the policy, and refresh when it reports a
change. An eslint no-restricted-syntax rule blocks direct CipherService
lookups in Autofill.
main.background.ts takes only the policy's hunks. CipherService keeps
its messagingService argument (B5), and the revealedCipherService
override and the public messageListener stay out (A10).
* win_webauthn: Add raw GetAssertion types and functions
* win_webauthn: Add safe wrappers for GetAssertion
* win_webauthn: Support the appid extension in GetAssertion
* [PM-27100] Add the autotype client models, draft
* [PM-27100] URI label change
* [PM-27100] Move autotype pairing data schema to libs/common
* [PM-27100] Add more comments
* [PM-27100] Update this PR based on schema 1.0.0 change from #24468
* [PM-27100] Retain unknown params in uri for future optional compatability
* [PM-27100] Handle non-empty strings
* [PM-27100] Small tests change
* [PM-27100] Small comment change
* [PM-27100] Remove (URI) from text
Takes the access connectors list, detail page and dialogs from pam/uat
byte for byte, deletes rotation/skeleton-delay.ts now that no tab reads
it, and moves the web strings: 27 added, 30 removed, and a corrected
description on pamAccessConnectorAssignmentsNone.
Associates the cloud web vault domains with the Bitwarden iOS and desktop
apps for passkey (webcredentials) support. The iOS app IDs match those
currently served at https://bitwarden.com/.well-known/apple-app-site-association;
the desktop app IDs are added for desktop and safari extension login with passkey.
* [PM-43327] feat: Add Privileged Controls seat adjustment to organization subscription page
Organizations with a Privileged Access Management subscription had no
self-serve way to change their PAM seat count or seat limit; changes
required a sales-assisted flow. This adds a seat adjustment section to
the vnext subscription page, mirroring the Secrets Manager pattern, and
wires it to the new privileged-controls subscription endpoint.
The section is gated behind PM39883_PamBillingSupport and hidden for
orgs on a sales-initiated PAM trial or with a canceled/pending-cancel
subscription, since seat changes are not meaningful in those states.
* Send the seat change as an adjustment instead of an absolute total
Review feedback: a stale form value could undo a concurrent autoscale or
another owner's change when the client sent the full seat count. The
server now adds the adjustment to its current count, so limit-only saves
send 0 and never move seats.
* Replace the seat minimum with the Password Manager seat cap
Review feedback alongside server PM-45759: the minimum is no longer
returned or enforced. Seats are now 1 to the Password Manager seat
count, with the maximum shown as the hint. When Password Manager has an
autoscale limit the Privileged Controls limit is required and capped at
it; otherwise the limit stays optional.
* Keep the Privileged Controls seat limit optional when Password Manager has one
* [PM-44244] feat: Let Owners remove Privileged Controls on the subscription page
Owners of an Enterprise organization with Privileged Controls get a
Remove Privileged Controls button next to Save in the Privileged Controls
section of the vNext subscription page. Confirming calls the new
DELETE /organizations/{id}/billing/subscription/privileged-controls
endpoint (bitwarden/server#8776), shows a success toast, forces a sync
so the locally stored organization drops usePam everywhere it is read,
and refreshes the page so the section disappears.
The remove button carries bitFormButton so Save and Remove cannot run at
the same time. The section is now also hidden for provider-managed
organizations, matching the server's standalone-owner requirement on
both the PUT and DELETE routes.
No Secrets Manager removal flow exists to mirror; the design follows the
Remove sponsorship pattern on the same page. Stacked on #24069.
* Guard the awaited sync and the Save/Remove lockout in specs
* Assert the confirmation dialog opens and describe the new message keys
* Update sdk-internal to 0.2.0-main.1230
* Drop obsolete AccessBadgeState cast in cipher-view-banner spec
`AccessBadgeState` now includes "unavailable" as of sdk-internal
0.2.0-main.1224, so the version-gated `UNAVAILABLE` double cast is no
longer needed. The literal assigns directly at each call site.
---------
Co-authored-by: bw-ghapp[bot] <178206702+bw-ghapp[bot]@users.noreply.github.com>
* PAM (3-A7): bring the managed credentials tab to its pam/uat state
Extracts A7 from pam/uat. The managed credentials list, add, detail and
edit pages follow the rotation design. Rotate now asks for confirmation
first and names the pause when a paused credential is still rotating.
The history explains each job in a Details column and opens the job
drawer, and dates read "Nov 4, 2026" through the new CalendarDatePipe.
rotation-detail-status.ts and its spec come with it: only the config
edit page reads them, and they need this tab's RotationRowStatus.
Web strings: +88, -30, including pamCollectionFilter.
* [PAM] Stop rotation polling on leaving, and confirm Rotate now from the saved config
The router keeps the shell route's providers alive after leaving it, so
RotationConfigsService never reached ngOnDestroy and kept re-reading the list
every 5 seconds. The shell now stops polling when it's destroyed, and nothing
restarts it until the next load.
The detail page's Rotate now asked for the sign-out confirmation based on the
unsaved checkbox, while the server rotates with the saved setting. It now reads
the saved config, matching the list's row menu.
* [PAM] Drop the HTML comments from the managed credentials templates
* [PAM] Back off rotation polling, and poll the detail page while a job runs
The list re-read every 5 seconds for as long as any job ran, and retried after
a failed read. The detail page read the config once after Rotate now and stayed
on Rotating until a manual reload.
Both now share ActiveJobPoller: reads wait 10s, doubling to at most 2 minutes,
a run gives up after 8 reads or the first failure, and one read is in flight at
a time. A run restarts on the next load or Rotate now. The timer runs outside
the Angular zone so whenStable() still settles.
* PAM (3-A5): bring the vault list's controlled access filter to its pam/uat state
Extracts A5 from pam/uat. The Controlled access filter service and the
table chip move from bit-web to bit-pam-components, so the popup can
use them, and bit-web imports them from there. The table chip gains an
Ending soon option, the badge's coloured tiles and a chip icon. The
legacy vault sidebar's Controlled access group goes: PAM no longer
provides VAULT_CONTROLLED_ACCESS_FILTER, which the sidebar injects as
optional.
The gated shared folder banner and filter indicator say "Shared folder"
through pamSharedFolderRequiresRequest.
Web strings: +2, -1. Browser strings: +4, for the popup's filter.
* [PAM] Split sameMatches' set comparison into a guard and a return
Extracts A3 from pam/uat. The audit log and its event drawer show times
in the "Nov 4, 2026" format through TimestampPipe, and the time period
filter shows the full time. Custom always reopens the date picker, and
an applied custom range gets its own row and chip label ("Nov 1, 2026 –
Nov 4, 2026", "From …", "Until …"). The CSV export writes timestamps and
extended-until in the exporter's local time with the UTC offset, and
the granted duration through durationText.
It removes A2's durationLabel shim and the pamInboxDuration* keys it
read. pamAuditIncompleteTooltip becomes pamAuditOutcomeUnconfirmedTooltip
for its new copy.
Extracts A4 from pam/uat. The item view banner becomes one card per
state (request, pending, approved, active, ended, unlicensed and
unavailable) under a shared card header. Request access opens a form
that keeps its height while the pre-check loads, in a dialog on web and
a sheet in the popup (CIPHER_VIEW_BANNER_LAYOUT). An approved request
says until when, and Cancel sits inside the pending card.
It removes A2's two shims: labelKey on the requester's duration presets,
and the optional cap on ExtendLeaseDialogComponent.open.
Browser strings are the ones the popup banner reads once PAM ships in
the extension.
* PAM (3-A6): bring the rotation shell and shared helpers to their pam/uat state
Extracts the rotation shell, routes and breadcrumb, the assignment picker,
the schedule input and the shared rotation helpers (schedule labels,
relative times, timestamps, the create flow and the managed credential
draft) from pam/uat, with the web strings they read.
skeleton-delay.ts stays until A9, whose tabs still import it.
rotation-detail-status.ts moves to A7, since it reads A7's
RotationRowStatus and only A7's config edit page uses it.
From the A9 files, the access connector detail takes pam/uat's breadcrumb
binding, as the breadcrumb no longer has a truncate input, and its spec
drops the test that expects a disabled picker to repeat its tooltip as a
hint, which pam/uat's spec no longer has either.
* PAM (3-A6): leave the target system tab routes to the target systems extraction
main's target system page has no tabs and leaves with [".."], which a
:tab segment resolves back to the same page through the bare-id
redirect. The routes go with the page that reads them.
* PAM (3-A6): drop TargetSystemKind.ActiveDirectory until the SDK bump that adds it
* PAM (3-A2): bring access requests to their pam/uat state
Extracts the access requests page, its approvals, history and My
requests tabs, the request dialog and request summary from pam/uat,
with the bit-pam and bit-pam-components helpers they introduce.
Three shims keep main's audit page and item view banner compiling
until A3 and A4 land: durationLabel stays next to durationText, the
requester presets keep labelKey, and the extend dialog's cap is
optional. ACCESS_BADGE_LOOK and the badge's readyLabelKey input move
here from A4, as new exports A4 then has nothing to undo.
* PAM (3-A2): bring the access-state badge and listMyLeases(userId) to their pam/uat state
* PAM (3-A2): drop the HTML comments and trim narrating code comments
* PAM: type the setInterval call filter so the Storybook build compiles the approvals spec
* PAM: scope the Filtered stories' play functions to the toolbar chip and its menu
Relocates the JWT decode utility to a new libs/common/src/auth/jwt feature
folder. This removes the restricted libs/common -> @bitwarden/auth/common
import from TokenService.
* [PM-45874] Add extension welcome page behind feature flag
* [PM-45874] Remove VFO1 flag references from welcome page
* [PM-45874] Update welcome page background and spacing to match design
* [CL-762] Migrate libs/components to OnPush and signals
Add OnPush change detection to the remaining components and test/story
hosts, converting state that changes outside input/event triggers to
signals so templates stay in sync.
* [CL-762] Migrate UIF-owned app layout components to OnPush and signals
Covers the browser popup footer and extension anon layout wrapper, and the
web layouts, org switcher, and product switcher.
* [CL-762] Restore Signal import in user layout
* [CL-762] Migrate remaining UIF signal suppressions
Convert the menu-item and tab-link disabled inputs, the resize-observer and
password-input-toggle outputs, and the product/navigation switcher story
mock inputs to signals.
* Implements new filters for table v2 on members page
* Implement policies filter on Table V2 members page
* Fix dropdown for filter
* As directed by design review, remove the groups filter icon. Don't need the icons in the filter chips