Group Admins

Add or remove group admins on an existing group conversation. Admins can manage group settings, permissions, and membership depending on your groupPermissions flags.

Set type to add or remove, and pass the affected chat user ids in the groupAdmins array. The response returns the updated conversation document.

Use Group Admins when:

• A group owner promotes a member to admin from the SDK group settings screen.
• You demote an admin back to a regular member (type: remove).
• You batch-promote multiple members after a role change in your app.
• You sync admin lists from an external workspace or org chart.

Part of the Chat Conversation APIs for the chat package / SDK — not Platform → Conversations. Requires a chat user Bearer token with sufficient group privileges (typically owner or existing admin).

Add admins — promote one or more participants:

{
  "conversationId": "694b...d8",
  "type": "add",
  "groupAdmins": [
    "694b...a1"
  ]
}

Remove admins — demote admins back to regular members:

{
  "conversationId": "694b...d8",
  "type": "remove",
  "groupAdmins": [
    "694b...a1"
  ]
}

On success, data.conversation reflects the updated groupAdminslist. The success message varies by operation (for example "Admins added successfully").

{
  "success": true,
  "message": "Admins added successfully",
  "data": {
    "conversation": {
      "_id": "694b...d8",
      "conversationType": "group",
      "groupName": "Dev Team",
      "groupDescription": "Sprint coordination",
      "groupImage": null,
      "participants": [
        "694b...a1",
        "694b...a2",
        "694b...a3"
      ],
      "groupAdmins": [
        "694b...a3"
      ],
      "owner": "694b...a3",
      "groupPermissions": {
        "onlyAdminCanSendMessage": false,
        "onlyAdminCanEditInfo": false,
        "senderCanEditMessage": true,
        "allowMemberAdd": true,
        "allowMemberRemove": false,
        "moderationEnabled": false
      },
      "unreadCount": {},
      "pinnedMessage": [],
      "lastMessage": "70a1...c4",
      "metadata": {
        "workspaceId": "c1"
      },
      "createdAt": "2026-07-10T09:00:00.000Z",
      "updatedAt": "2026-07-10T09:00:00.000Z"
    }
  },
  "error": null
}

Admin changes fail when the token is invalid, the conversation does not exist, the caller lacks admin privileges, or the payload is malformed.

{
  "success": false,
  "message": "No token, authorization denied",
  "data": null,
  "error": "Unauthorized"
}

{
  "success": false,
  "message": "Access denied: insufficient permissions",
  "data": null,
  "error": null
}

{
  "success": false,
  "message": "Conversation not found",
  "data": null,
  "error": null
}

{
  "success": false,
  "message": "type must be add or remove",
  "data": null,
  "error": null
}

• Only promote users who are already in participants; add them first via Group Participants if needed.
• Avoid removing the last admin unless transferring ownership — keep at least one admin for manageable groups.
• Refresh the SDK group settings UI from data.conversation.groupAdmins after each successful PATCH.
• Gate promote/demote actions in your UI based on the caller's role (owner vs admin) and your product rules.