@@ -90,13 +90,21 @@ public function create($parent, Membership $postBody, $optParams = [])
90
90
* authentication](https://developers.google.com/workspace/chat/authenticate-
91
91
* authorize-chat-user) You can authenticate and authorize this method with
92
92
* administrator privileges by setting the `use_admin_access` field in the
93
- * request. (members.delete)
93
+ * request. To delete memberships for space managers, the requester must be a
94
+ * space manager. If you're using [app
95
+ * authentication](https://developers.google.com/workspace/chat/authenticate-
96
+ * authorize-chat-app) the application must be the space creator.
97
+ * (members.delete)
94
98
*
95
99
* @param string $name Required. Resource name of the membership to delete. Chat
96
100
* apps can delete human users' or their own memberships. Chat apps can't delete
97
101
* other apps' memberships. When deleting a human membership, requires the
98
- * `chat.memberships` scope and `spaces/{space}/members/{member}` format. You
99
- * can use the email as an alias for `{member}`. For example,
102
+ * `chat.memberships` scope with [user
103
+ * authentication](https://developers.google.com/workspace/chat/authenticate-
104
+ * authorize-chat-user) or the `chat.memberships.app` scope with [app
105
+ * authentication](https://developers.google.com/workspace/chat/authenticate-
106
+ * authorize-chat-app) and the `spaces/{space}/members/{member}` format. You can
107
+ * use the email as an alias for `{member}`. For example,
100
108
* `spaces/{space}/members/example@gmail.com` where `example@gmail.com` is the
101
109
* email of the Google Chat user. When deleting an app membership, requires the
102
110
* `chat.memberships.app` scope and `spaces/{space}/members/app` format. Format:
0 commit comments