Repository navigation
feat: add doc for seat-based billing plans - #3414
paddycarver merged 28 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
When testing and clicking the "new organization plan" hyperlink, the org plan is in a disabled state. Are there certain pre-reqs to create a plan, and if so, do we expect customers on this doc to have already met those? |
@ssibley-clerk I'm assuming by "org plans is in a disabled state" you mean that the "Enable organization billing" toggle is off. We currently allows users to create plans while this toggle is off. We surface in the UI a warning stating that the toggle is off if plans were created for orgs. 
|
I personally don't think so. @paddycarver |
This reverts commit 04ab835.
| > [!IMPORTANT] | ||
| > | ||
| > - Organizations subscribed to Plans that are not seat-based will have their membership limit set to the [default membership limit](/docs/guides/organizations/configure#membership-limits). This can be overridden on a per-Organization basis. | ||
| > - If an Organization's seats are forcibly reduced (for example, when its Subscription ends), the Organization will keep its currently provisioned seats but cannot invite new members until it is under the new seat limit. | ||
| > - When an Organization is on a seat-based Plan, you cannot manually set the Organization's seat limit. |
There was a problem hiding this comment.
This callout feels out of place to me because it talks more about seat-based limits than per-seat pricing. We could move it down under Managing seat limits for e.g., and even make it a paragraph rather than a callout. But open to suggestions @l-armstrong @paddycarver
There was a problem hiding this comment.
The complicated thing to navigate here is there are two different types of seat limit: there's the maximum number of seats that can be purchased under a plan, period, and then there's the number of members the Organization can have without purchasing more seats.
When there was just plan limits, these two numbers were the same. With per-seat pricing, these two numbers are usually different.
These three bullets apply to the number of seats that an Organization has / the number of members the Organization can have without purchasing more seats, a concept that applies to both plan limits and to per-seat pricing.
I'm not sure I have an opinion on where to put it, but I wanted to info dump quick on some of the complexity when we talk about "seat limits".
There was a problem hiding this comment.
I just moved it to "managing seat limits", and I think we're on board with that -- do you like that, or is putting it at the top better?
This branch was successfully deployed
7 participants
🔎 Previews:
What does this solve? What changed?
Deadline