Repository navigation
Docs: drop the group concurrency figure, point at pricing instead - #617
Open
amitthacker-maker wants to merge 1 commit into
Open
amitthacker-maker wants to merge 1 commit into
amitthacker-maker wants to merge 1 commit into
Conversation
The constraints table read "100,000 (up to 10,000 concurrent)" for the maximum users in a group. Concurrency is not a group property. It is sold per plan as a share of monthly active users, so there is no single number that belongs in a group-limits row, and the figure was being read as a product ceiling. The value cell is now 100,000 with no concurrency figure, and the notes cell says concurrent connections are part of your plan and links the pricing page, which is the authority on them. Deliberately untouched: the typing indicators row and the "for performance" wording on this page. Both wait on an open engineering question about whether the large-group configuration switches off receipts only or receipts and typing. No other page in the repository states a concurrency figure for a group. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The constraints table read "100,000 (up to 10,000 concurrent)" for the maximum users in a group.
Concurrency is not a group property. It is sold per plan as a share of monthly active users, so there is no single number that belongs in a group-limits row. Printing one there invites it to be read as a product ceiling, which is how it has been read.
What changes
The value cell becomes
100,000with no concurrency figure. The notes cell gains a sentence saying concurrent connections are part of your plan, linking pricing, which is the authority on them.No other page in the repository states a concurrency figure for a group, so this is the only edit needed.
Deliberately untouched
The typing indicators row and the "for performance" wording on this same page. Both wait on an open question: does the large-group configuration switch off receipts only, or receipts and typing? This page's own row header says "without receipts" while its notes column says "and typing indicators", and
articles/properties-and-constraintsagrees with the notes. Until that is settled, changing the wording would mean picking a side.🤖 Generated with Claude Code