Windows/macOS
Group
Update time: 2023/03/23 03:58:14
Team types
CommsEase IM SDK provides the team chat features in two types: ordinary team and advanced team. The advanced team has more operation permissions, and The APIs are kept consistent under common operations.
- Similar to a discussion team or fast group session in the current IM chat application, without team operation authority, an ordinary team applies to the scene of rapid creation of a group session. Each ordinary team can only have one manager. Both the administrator and ordinary members may add members to and remove members from a team. New members may be added without the consent of the others.
- An advanced team has more complete and abundant features, and is subject to more restrictions on authority. An advanced team has all the features of an ordinary team. An advanced team is recommended for development.
The detailed differences between the two in features are as follows:
| Features | Ordinary team | Advanced team |
|---|---|---|
| Capacity | IM pro 200 persons/team, expanded up to 500 persons/team (value-added feature) | IM pro 200 persons/team, expanded up to 500 persons/team (value-added feature) |
| Create | Specify team type at creation | Specify team type at creation |
| Team information | Team name, profile picture, profile, announcement, extension field | Team name, profile picture, profile, announcement, extension field, Verification mode for team invitation, team invitation mode, invited mode, Team information modification mode, modification mode of team profile extension field |
| Invite a user to a team | All team members may invite other users to the team, which cannot be configured | Supported configurations: Only the administrator can invite to the team, all members can invite to the team. |
| Invitee consent mode | Invitee's consent not required, which cannot be configured | Supported configurations: Invitee's consent required Invitee's consent not required |
| Apply for joining a team | Not supported | Supported |
| Group verification | By default, the verification is not required. | Three options are available. The verification is required; The verification is not required; Anyone is not allowed to join the group. |
| Group member types | Team owner, ordinary members | Group owner, administrators, and members. |
| Designate an administrator | Manager setting not allowed | A team owner may add and remove members. |
| Authority to update team profile | Everyone may make modifications | Supported configurations: Only the administrator may make modifications, everyone may make modifications. |
| Modify the nicknames of team members | Not supported | A owner may update the nickname of everyone in a team. The administrator can only update the nicknames of ordinary members in the team. |
| Modify my nickname in the team | Not supported | Supported |
| Supported message types | Similar to basic message types. | Similar to basic message types. |
| Message notification | Receive notifications, reject notifications | Receive a notification, only receive the administrator's message notifications, reject notifications |
| Historical messages | Support cloud message history; standard IM may acquire the history record for the recent 1 year; support the expansion to 3 years at most (value-added feature). |
Support cloud message history; standard IM may acquire the history record for the recent 1 year; support the expansion to 3 years at most (value-added feature). |
| Offline messages | At most 100 offline messages are sent in each team chat session. | At most 100 offline messages are sent in each team chat session. |
| Message roaming | Automatically roam recent 100 messages in each session within 7 days. | Automatically roam recent 100 messages in each session within 7 days. |
| Forcibly send push notifications to specified members | Supported | Supported |
| Read receipt | Supported, only applicable to the team of no more than 100 members. | Supported, only applicable to the team of no more than 100 members. |
| Remove | Only the owner has the authority to remove | Both the owner and the administrator have the authority to remove, and an administrator cannot remove the owner and the other administrators out of the team. |
| Actively leave the team | Anyone of an ordinary team can actively leave the team; If the owner leaves the team, the team will not have an owner. |
Except the owner, other users may actively leave the team. A owner cannot quit the team until he/she transfers the team to other team members |
| Mute | Not supported | Administrators mute or unmute ordinary members |
| Transfer the team | Not supported | Owner may transfer the team owner's authority to other team members, and after the transfer, the transferee will become the new owner, and the transferor will become a ordinary member. Owner may also leave the team upon the transfer. |
| Dismiss a team | A creator may dismiss team; if a creator quits the team, other members will be unable to dismiss the team. | An owner may dismiss a team. |
For the charge for the value-added feature, see: Charge Description
Overall, an advanced team has covered all features of an ordinary team, and supports more powerful features. Therefore, an advanced team is recommended for the developer to flexibly support the types of ordinary team and advanced team.
Read receipt in a team
CommsEase IM SDK 5.0 introduces a new feature "read receipt in a team", with which the developer may easily check the read and unread details of a team message. CommsEase IM Demo demonstrates the feature and use method of "read receipt in a team", which may be used as a mode for reference.
The "read receipt in a team" feature only applies to an advanced team of no more than 100 members. If more than 100 team members, messages may be sent as usual, but the read receipt will not be provided, making it impossible to check the read and unread status of a message.
This is a paid service. If required, please contact our customer manager to enable the service.
Developer resources
For more information on the development guide for team features at each client, see: