source/administration-guide/manage/team-channel-members.rst (1)

162-165: Consider adding a minimal request + NDJSON response example.

A tiny concrete example would make integration/testing faster, especially for clients unfamiliar with streaming NDJSON.

Example doc snippet

 System admins can set the complete membership of a channel in a single API call using ``PUT /api/v4/channels/{channel_id}/members``. The request body is a JSON array of user IDs representing the desired membership. The server computes the diff against the current membership and adds or removes users as needed, leaving existing members untouched.
 
 Results are streamed back as NDJSON (``application/x-ndjson``), one line per batch. Each line contains ``added``, ``removed``, and ``errors`` arrays for that batch. Query parameters ``batch_size`` (default 100) and ``batch_delay_ms`` (default 500) control the processing rate.
+
+Example request body::
+
+  ["user_id_1", "user_id_2", "user_id_3"]
+
+Example NDJSON line::
+
+  {"added":["user_id_3"],"removed":["user_id_4"],"errors":[]}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@source/administration-guide/manage/team-channel-members.rst` around lines 162
- 165, Add a minimal concrete example showing a sample JSON request body and a
few NDJSON response lines for the PUT /api/v4/channels/{channel_id}/members
endpoint so readers can see the exact shape of input and streaming output;
include the endpoint path and show a tiny request array of user IDs and then 2–3
NDJSON lines demonstrating the batch objects with "added", "removed", and
"errors" arrays and note the query parameters batch_size and batch_delay_ms used
to produce the example.