From 6097642bf981bf59ed71ddc7fe8491d7de49959d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Wed, 4 Feb 2026 09:32:07 +0100 Subject: [PATCH] Apply suggestions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Kévin Commaille --- .../client-server-api/modules/invite_permission.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/content/client-server-api/modules/invite_permission.md b/content/client-server-api/modules/invite_permission.md index 0f292d47..5e5b2ac3 100644 --- a/content/client-server-api/modules/invite_permission.md +++ b/content/client-server-api/modules/invite_permission.md @@ -6,13 +6,13 @@ Users may want to control who is allowed to invite them to new rooms. This module defines how clients and servers can implement invite permission. -#### Events +#### Account data {{% event event="m.invite_permission_config" %}} #### Client behaviour -To reject invites from all users automatically, clients MUST add an [`m.invite_permission_config`](#minvite_permission_config) +To reject invites from all users automatically, clients MAY add an [`m.invite_permission_config`](#minvite_permission_config) event in the user's [account data](#client-config) with the `default_action` property set to `block`. To stop rejecting all invites, the same event without the `default_action` property MUST be added to the account data. @@ -20,8 +20,8 @@ added to the account data. When the `default_action` field is unset, other parts of the specification might still have effects on invites seen by clients, like [ignoring users](#ignoring-users). -When sending an invite to a user that blocks invites, clients SHOULD receive an error response with -the `M_INVITE_BLOCKED` error code. +Attempting to send an invite to a user that blocks invites will result in an error response with the +`M_INVITE_BLOCKED` error code. #### Server behaviour @@ -38,9 +38,8 @@ is invited: * [`PUT /_matrix/client/v3/rooms/{roomId}/state/m.room.member/{stateKey}`](#put_matrixclientv3roomsroomidstateeventtypestatekey), when the `membership` is set to `invite`. -In addition, existing events already in the database MUST NOT be served over client synchronisation -endpoints such as [`GET /sync`](#get_matrixclientv3sync). Invite events received over federation -should likewise not be served over `GET /sync` requests. +In addition, invite events for this user already in the database, or received over federation, MUST +NOT be served over client synchronisation endpoints such as [`GET /sync`](#get_matrixclientv3sync). Servers MAY return any suppressed invite events over `GET /sync` if invite blocking is later disabled.