Update plan tier hierarchy for sponsorship policies #6853
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

TL;DR
Updated plan tier hierarchy by swapping
starterandstarter_legacypositions, and lowered the required plan for sponsorship policies fromacceleratetostarter.What changed?
planToTierRecordForGatingby changing:starter_legacyfrom tier 1 to tier 2starterfrom tier 2 to tier 1acceleratetostarterin theGatedSwitchcomponentHow to test?
starterplan can now access sponsorship policiesstarter_legacyplans maintain their expected access levelsWhy make this change?
This change makes sponsorship policies available to more users by lowering the tier requirement. The plan hierarchy adjustment ensures that the
starterplan is positioned correctly in the tier structure, making it more accessible than the legacy version while maintaining the proper feature gating across the platform.