From 5934fe701826a3f6b2795080592d3279867d315c Mon Sep 17 00:00:00 2001
From: DMRobertson <DMRobertson@users.noreply.github.com>
Date: Thu, 21 Jul 2022 10:27:55 +0000
Subject: deploy: 4f57ef0b1810bef6071d23e32785623de8b48fdf

---
 develop/usage/configuration/config_documentation.html | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'develop/usage/configuration/config_documentation.html')

diff --git a/develop/usage/configuration/config_documentation.html b/develop/usage/configuration/config_documentation.html
index f6800cc54a..6b71c309ed 100644
--- a/develop/usage/configuration/config_documentation.html
+++ b/develop/usage/configuration/config_documentation.html
@@ -1417,6 +1417,7 @@ limit only, as Synapse presumes ratelimiting by room will be done by the sending
 <p>The <code>rc_invites.per_user</code> limit applies to the <em>receiver</em> of the invite, rather than the
 sender, meaning that a <code>rc_invite.per_user.burst_count</code> of 5 mandates that a single user
 cannot <em>receive</em> more than a burst of 5 invites at a time.</p>
+<p>In contrast, the <code>rc_invites.per_issuer</code> limit applies to the <em>issuer</em> of the invite, meaning that a <code>rc_invite.per_issuer.burst_count</code> of 5 mandates that single user cannot <em>send</em> more than a burst of 5 invites at a time.</p>
 <p>Example configuration:</p>
 <pre><code class="language-yaml">rc_invites:
   per_room:
@@ -1425,7 +1426,11 @@ cannot <em>receive</em> more than a burst of 5 invites at a time.</p>
   per_user:
     per_second: 0.004
     burst_count: 3
+  per_issuer:
+    per_second: 0.5
+    burst_count: 5
 </code></pre>
+<p><em>Changed in version 1.63:</em> added the <code>per_issuer</code> limit.</p>
 <hr />
 <h3 id="rc_third_party_invite"><a class="header" href="#rc_third_party_invite"><code>rc_third_party_invite</code></a></h3>
 <p>This option ratelimits 3PID invites (i.e. invites sent to a third-party ID
-- 
cgit 1.5.1