feat: add doc for seat limit based plans for Clerk Billing#3266
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
paddycarver
left a comment
paddycarver
left a comment
There was a problem hiding this comment.
I think I'd like to also document that once a plan is created, you can't add, remove, or change the seat limit on it.
It would be nice to explicitly say somewhere that organizations on plans without seat limits on them will have their membership limit controlled by the max member limit on the instance, and that starting a plan with a seat limit will always use the plan's seat limit, and that stopping a plan with a seat limit will revert to the default limit. I know you gesture at it when talking about what happens if you want to switch to a non-seat-based plan, but it would be nice to say it directly, not couched in a conditional.
It would be nice to document that if an organization is over the seat limit and is forcibly moved to a plan with a lower seat limit (C1 moves them, subscription ends, etc.) they will be allowed to keep their currently-provisioned seats but they cannot invite anyone new until they're under the new seat limit.
It would be nice to call out that you need the Core 3 SDK to have information about seat limits show up in the UI.
It would be nice to mention that you cannot manually set an organization's seat limit while they're on a seat-based plan.
That's all the stuff I can think of at the moment 😄
|
For calling out core 3 versions, you can use the version numbers from this PR clerk/javascript#8166 and copy the structure from this warning https://github.com/clerk/clerk-docs/blob/main/docs/guides/development/custom-flows/authentication/email-password.mdx?plain=1#L9-L18 |
- Update page title to "Plans with seat limits" to match manifest nav entry - Write a more descriptive frontmatter description instead of restating the title - Capitalize "Plan" consistently as a proper noun, matching sibling billing docs - Bold UI element labels (Seat-based, Unlimited members, New Organization plan) - Change "in your instance's settings" to "in the Clerk Dashboard" per conventions - Replace "convey" with "allow" for clearer wording on unlimited seats - Hyphenate compound adjectives: "seat-limited", "non-seat-limited" - Extract SDK version requirements from the dense IMPORTANT callout into its own section for better scannability - Fix "instance's max member limit" to "default membership limit" to match the established product term used in org configuration docs and later in this same page; added cross-reference link to the membership limits configuration section Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
| > | ||
| > - Plans created with seat limits cannot have the seat limit removed or changed. Similarly, Plans created without seat limits cannot have seat limits added after the Plan is created. | ||
| > - Organizations subscribed to Plans with seat limits on them will have their membership limit set to the Plan's seat limit. | ||
| > - Organizations subscribed to Plans without seat limits 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. |
There was a problem hiding this comment.
We changed "instance's max member limit" to "default membership limit" here to align with the established product term used in the org configuration docs and with line 50 of this same page, which already uses "default membership limit." We also added a cross-reference link for discoverability.
If "max member limit" was intentionally referring to a different, harder ceiling distinct from the configurable default, let us know and we'll revert this.
|
Thanks for the new doc! I made a pass to align it with the conventions in the sibling billing docs. Here's what changed in c6ef37f:
|
Use "a Plan without seat limits" instead of "a non-seat-limited Plan" to match the phrasing already used earlier in the same doc. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
4 participants
🔎 Previews:
What does this solve? What changed?
Deadline