Team plan full rollout

[aj-codecov]

On November 16th, 2023 we launched the Team plan, a lower cost offering designed to get people in the Codecov door. We've seen people purchase roughly 1.2 team plans per day over the first 25 days (not adjusted for weekends). We're now eyeing a more "first class citizen" rollout of the Team plan. This means it will be present on our pricing page and supported forevermore.
Additionally, our current free offering will need to be scoped to be a patch only offering.

What does this entail?

• API → need to hide project coverage, tons of work
• Flags and component features need to not be used at the point of ingestion (need to add checks)
• We should give users a heads up that these features are going away
• since it’s not that many users (15 users currently) can just send email
• Worker changes may not be needed, we should continue to store data in-case user upgrades
• Browser extension, slack app, VSCode extension
  • browser extension has no concept of plan - api changes are prob enough
  • slack app will require changes in API as well as the app itself

Risks to extensions
Making changes to the API will have a risk of breaking each of the extensions:

• VSCode
• Browser
• Slack app
• PR comment

We will need further investigation (and code changes) on these extensions before deploying the API changes. (ie Issues 1157-1160)

However Issues 1148 - 1151 can be completed before the investigations since they are foundational work that don't actually modify the responses of the endpoints

Pre-work

Beta Give feedback

1. Technical planning for Team Plan full rollout for API #968
   investigation +1
   
2. Investigate impact of this change on VSCode extension #1157
   +0
3. Investigate impact of this change on Browser extension #1158
   +0
4. Investigate impact of this change on Slack app #1159
   +0
5. Investigate impact of this change on PR comment #1160
   +0
6. Investigate impact to docs #1684
   +0

1st

Beta Give feedback

1. Create DB tables for org permissions #1148
   +0
2. Add to admin page to insert new permissions and tiers into the DB #1149
   +0
3. Populate tables with default permission values #1150
   +0
4. Add logic to retrieve org permissions by a given Owner and code to gate access #1151
   +0
5. Update REST internal endpoints, add permission levels to necessary serializers #1152
   0 of 7
   +0
6. Update REST public endpoints, add permission levels to necessary serializers #1153
   0 of 17
   +0
7. Update GraphQL endpoints, add permission levels to necessary resolvers #1154
   0 of 9
   +0

The work below is likely doable at the same time as some of the above work as it's 75/25 platform/applications

2nd

Beta Give feedback

1. Team Plan cont. (disabling project coverage centric yaml configs) #1628
   +0
2. Private repos on Developer Plan have the same experience as Private repos on Team plan (and not that on Pro) #1653
   P2: stretch epic +2
   

   

[aj-codecov]

Upgrade levers - where can we reasonably put these? What makes sense at the free and Team level?
Notification for free users should be well in advance - preferred approach would be to change the users-basic plan and not add a new plan. If blocker we can revisit. Email/in app messaging. Can we target ONLY users using flags/components in a private repo.

VSCode extension - no change needed to what's shown, labeling to show plans it applies to in the results and descriptions.
Slack app - needs to remove change and focus on PR/Commit focus - what's the usage?
Public API - needs to remove change and focus on PR/Commit focus - maybe not possible?

Framework: sensitive to removal, less sensitive to accidental discovery of non-core features

[katia-sentry]

Team plan Rollout product doc: https://www.notion.so/sentry/Team-Plan-Full-Rollout-de14b39879e24edcab532719f2c51ad2

[katia-sentry]

team plan ramifications on public api investigation #651

[katia-sentry]

We should setup project gate in VSCode extension for folks that try to setup project coverage on team plan