[PM-39129] Add UsePam organization capability#7816
Conversation
🤖 Bitwarden Claude Code ReviewOverall Assessment: REQUEST CHANGES This PR adds a Code Review Details
Dependency ChangesNo dependency manifest changes. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7816 +/- ##
==========================================
+ Coverage 61.25% 65.67% +4.41%
==========================================
Files 2193 2193
Lines 97296 97323 +27
Branches 8767 8767
==========================================
+ Hits 59601 63914 +4313
+ Misses 35582 31201 -4381
- Partials 2113 2208 +95 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Self-hosted organizations are created via OrganizationFactory.Create (from a license or its claims) rather than Organization.UpdateFromLicense, so UsePam must be mapped there as well. Without it, an org provisioned from a PAM-enabled license would default to UsePam = false.
connerbw
left a comment
There was a problem hiding this comment.
Billing changes look good
1d8caba to
8399deb
Compare
|



🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-39129
📔 Objective
Add the UsePam organization ability across the stack, modeled on
UseInviteLinks/UseMyItems:OrganizationAbility+ profile/provider detail modelsDefaults off for all organizations. Plan/pricing wiring is deliberately deferred until a PAM plan tier exists, so the Admin toggle is currently the only way to enable it.
📸 Screenshots