[PM-19009] Remove feature flag 'pm-15179-add-existing-orgs-from-provi…

[jonashendrickx]

…der-portal'

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-19009

📔 Objective

The dropdown options are

New organization

Existing organization

Selecting “New organization” triggers the existing workflow

Selecting “Existing organization” triggers a new workflow (see figma design)

Both the Provider Admin and Service User has permissions to select both buttons. If the assigned seats exceed the available seats for an organizations, a Service User will not be able to select that organization.

Add an “Add existing organization” option to the Provider Portal. Given a user is a member of a Provider Portal AND an Owner of an organization, then the user can add that organization to the Provider Portal.

The transition from a non-managed organization to a managed organization will require a billing migration. We should leverage the consolidated billing migration for this. The following qualifies as an existing organization that can be migrated:

has an active subscription

the active provider user (any role) is an Owner of the organization

a service user can only add organizations that is within the provider’s seat minimum. The organization will be in a disabled state if the organization seats exceed the provider’s available seats.

📸 Screenshots

Screen.Recording.2025-04-08.at.21.37.36.mov

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

LaunchDarkly flag references

❌ 1 flag removed

Name	Key	Aliases found	Info
Add existing orgs from Provider Portal	pm-15179-add-existing-orgs-from-provider-portal		✅ all references removed

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Checkmarx One – Scan Summary & Details – abab2785-fd2e-45fa-aa70-170185ade0e6

Great job, no security vulnerabilities found in this Pull Request

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.91%. Comparing base (ad05e3f) to head (f6795d5).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5579   +/-   ##
=======================================
  Coverage   44.90%   44.91%           
=======================================
  Files        1558     1558           
  Lines       70994    70991    -3     
  Branches     6339     6338    -1     
=======================================
  Hits        31883    31883           
+ Misses      37762    37759    -3     
  Partials     1349     1349           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.