Skip to main content

Group channel overview

Group channels enable multi-user communication, typically involving two or more users. The Nexconn Chat group channel service provides rich member management and mute features, supports offline message push and historical message roaming, and is suitable for interest groups, work teams, and customer service scenarios. Chat UI offers ready-to-use group channel UI components.

Service configuration

The client SDK supports group channels by default without requiring activation. Some basic features and value-added services can be enabled and configured in the console under Service Purchase and Service Configuration pages for IM services.

  • There is no limit to the number of group channels that can be created under an App Key. A single user can join an unlimited number of groups.
  • Group channels have a member capacity limit, with a default maximum of 3000 members. You can submit a ticket to modify this limit.
  • By default, the cloud storage for group messages service is not enabled for an App Key. You can enable this service in the console. For production App Keys, only Starter and Pro plans can enable this service.
  • By default, users can only view group messages sent after they joined. When historical message access for new members is enabled, new members can retrieve group messages sent before they joined..

Client SDK notes

  • Chat SDK provides hosted user profile and group profile capabilities by default. Chat UI uses the hosted profile data to display user names, avatars, group names, group avatars, and group member cards.
  • You can still implement Chat UI data source interfaces when you need to override hosted profile display data, integrate an existing business profile service, or customize the member list used by mention selection. See User information.
  • Chat SDK provides client APIs for group profile, member profile, and advanced group business operations, including group ownership, administrators, announcements, invitations, and group ID search. These flows do not require Server API calls unless your app needs additional server-side business orchestration.