Skip to content

Docs: add a group member limits page explaining the 300 figure - #615

Open
amitthacker-maker wants to merge 1 commit into
cometchat:mainfrom
amitthacker-maker:docs-fix/group-member-limits
Open

amitthacker-maker wants to merge 1 commit into
cometchat:mainfrom
amitthacker-maker:docs-fix/group-member-limits

Conversation

@amitthacker-maker

Copy link
Copy Markdown

Adds a page answering a question our docs have only ever answered as table rows: how many members can a group have, and why the number changes.

Why

The group limits live in the Users and Groups table on Properties and Constraints, with no explanation on any row. A reader, or an AI assistant quoting us, finds 300 and nothing about what it depends on. One of our own pages read that 300 as a performance ceiling.

It is a feature switch. Delivery and read receipts cost per-member work on every message, so turning them off raises the member cap by more than two orders of magnitude.

What this adds

  • articles/group-member-limits.mdx, registered in docs.json beside articles/properties-and-constraints in the Troubleshoot group.
  • A link from all five SDK group overviews (android, flutter, ios, javascript, react-native), which is where a developer asking this question actually is. Those pages open with an AI quick-reference accordion, so the link is a short closing section rather than a note above it.

The page also explains something the table leaves ambiguous: two rows carry the number 300 and they do not mean the same thing. One is a cap on how many members a group may hold. The other is a threshold on how many members are online at the same time. They share a number because receipts are the feature that sets the cap. A group with 500 members and 200 online gets no receipts, and not because of the online count: a receipts-on group cannot exceed 300 members in the first place.

And it surfaces the presence ceiling of 1,000 concurrent online users per app. That row is published in the constraints table but explained nowhere, it is app-wide rather than per group, and on a busy app it is reached before any of the group limits are.

Two things deliberately left narrow

The opening claim says "receipts off", not "receipts and typing indicators off". Our pages disagree on this. rest-api/groups/create.mdx labels that row "Maximum users in a group (without receipts)", receipts only, while its own Notes column and Properties and Constraints both add typing indicators. Until that is settled, this page claims only the part every page agrees on.

The typing row states the published threshold and nothing more. "Sent for groups with up to 1,000 online members", with no claim about whether large groups keep it. Both of these tighten in one line once the question above is answered.

On the title

The title is a question, which this docs set does not do elsewhere under /articles. It is deliberate: the aim is for the page title to match what someone actually types or asks. If that is not acceptable here, moving the question into the description is a two-line change.

🤖 Generated with Claude Code

…verviews

The group limit rows live only in the Users and Groups table on
Properties and Constraints, with no explanation on any of them, so a
reader or an answer engine finds 300 and nothing about why. One page
earlier read our 300 figure as a performance ceiling.

Adds articles/group-member-limits.mdx, registered in docs.json beside
Properties and Constraints in the Troubleshoot group, and linked from
the five SDK group overviews, which is where a developer asking this
question actually is.

The page says plainly that the limit is a feature switch and not a
ceiling: receipts cost per-member work on every message, so turning
them off raises the cap. It also explains that the two rows carrying
the number 300 do not mean the same thing, one being a cap on members
and the other a threshold on members online.

Two deliberate omissions. The opening claim is scoped to receipts
only, not "receipts and typing indicators off", because our pages
disagree about whether the large-group configuration switches typing
off as well: rest-api/groups/create.mdx labels that row "without
receipts" while its own notes column and Properties and Constraints
both add typing indicators. The typing row states the published
threshold of 1,000 online members and claims nothing about large
groups. Both can be tightened once that is settled.

Also surfaces the presence ceiling of 1,000 concurrent online users
per app, which is published in the constraints table but explained
nowhere, and which on a busy app is reached before the group limits
are.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Nov 17, 2026

Copy link
Copy Markdown

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit cc70fbb.

Approve preview

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants