Community channel overview
A community channel is a large-scale channel type with no upper limit on members. Community channels let users build social relationships and focus on topics of interest within high-volume communities. Each user can join up to 100 community channels. Within a community channel, all subchannels share a single member list. There is no limit on the total number of community channels in your app.
In server-side APIs, the busChannel parameter represents the subchannel ID, corresponding to the channelId parameter on the client side.
Activating the service
Community channels are available on the Pro plan and enabled by default.
Using subchannels
Community channels support creating independent subchannels (busChannel). Conversations, messages, unread counts, and member data are aggregated per subchannel, keeping message streams separate across subchannels.
Subchannels are classified as public or private. Public subchannels are open to all community channel members (no explicit join required) — every member receives messages sent to a public subchannel. Private subchannels are accessible only to users on their member list. For details, see Private subchannel overview.
Each community channel includes a default subchannel with the ID RCDefault. The RCDefault subchannel is open to all members and cannot be converted to a private subchannel.
If your app only needs a large group chat (beyond the 3,000-member group limit), you can use the community channel's unlimited membership and route all messages through the RCDefault default subchannel. Specify the subchannel ID as RCDefault when calling client and server APIs.
If you need a Discord-like structure with sub-communities, use your own custom subchannels exclusively. The default subchannel (RCDefault) and custom subchannels have behavioral differences — using only custom subchannels avoids these inconsistencies.
Community channel management APIs
Nexconn does not host community channel business logic — all business logic must be implemented on your app server.
For client developers, basic management operations such as creating community channels and subchannels only require interaction with your app backend. Your app backend calls the Nexconn Server API to create community channels, create subchannels, and perform other management operations.
The following table lists core community channel management APIs. For a complete list, see Endpoint list.
| Category | Description | Server API |
|---|---|---|
| Create / Dismiss | Provide a creator user ID, community channel ID, and name to create a community channel. Dismissing a community channel removes all member relationships. | Create a community channel, Dismiss a community channel |
| Join / Leave | After joining, the user can view new messages from that point forward. After leaving, the user no longer receives messages. | Join a community channel, Leave a community channel |
| Update info | Update community channel information used in push notification services. | Update community channel info |
| Create / Delete subchannels | Create independent subchannels within a community channel. Deleting a subchannel prevents further messaging in that subchannel. | Create a subchannel, Delete a subchannel |
| List subchannels | Retrieve the list of subchannels in a community channel. | List subchannels |
| Change subchannel type | Switch a subchannel between public and private at any time. | Change subchannel type |
| Add / Remove private subchannel members | Add or remove community channel members from a specific subchannel's private member list. The member list is enforced when the subchannel type is private. | Add private subchannel members, Remove private subchannel members |