Groups overview
Understand group profiles, members, join applications, roles, and group events in the OpenIM Flutter SDK.
In OpenIM, multi-user chat channels use Groups to govern shared metadata, member rosters, and permissions. The groupID uniquely identifies a group and is required for sending group messages, querying group details, managing member rosters, and handling join applications. In the current user's conversation list, the chat channel is identified and managed by conversationID; do not conflate the two identifiers.
Core data structures
| Structure | Purpose |
|---|---|
GroupInfo | Group name, avatar, announcement, owner, verification mode, member count, and extensions. |
GroupMembersInfo | A member's in-group nickname, role, mute status, and join details. |
GroupApplicationInfo | Join application records and resolution statuses. |
Group roles are defined in GroupRoleLevel: Ordinary members are 20, administrators are 60, and group owners are 100. UI views can toggle actions based on these levels, but final authorization is verified by OpenIMServer.
Group metadata and lifecycle
- Create a group
- Update group profile
- Set group announcement
- Set group join verification
- Set group member profile access
- Set group member friend permission
- Set group extension
- Join a group
- Quit a group
- Dismiss a group
- Get specified groups info
Group members and applications
Group moderation
State synchronization
Group-related notifications encompass joining groups, leaving groups, group profile updates, and group dissolutions. Register callbacks centrally within the application's single OnGroupListener. Use groupID as the merge key to update local group stores.
For member events, see Retrieving group members overview; for application events, see Group applications overview. Future completion, event delivery, and query recalibration are distinct operational phases.
The OpenIM Flutter SDK focuses on in-group metadata, member rosters, and permissions. Public group discovery and large-scale group capacity governance are coordinated between your business backend and OpenIMServer.
Was this page helpful?