From ff8a4cc39a62333efd0e27401cb721f08e4a3595 Mon Sep 17 00:00:00 2001
From: H-Shay <H-Shay@users.noreply.github.com>
Date: Thu, 24 Aug 2023 20:58:50 +0000
Subject: deploy: 5856a8ba4243a11f0d5f97ed2fe742ae31341452

---
 develop/usage/configuration/config_documentation.html | 10 ++++++++++
 1 file changed, 10 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 5f36d4b569..414593c55e 100644
--- a/develop/usage/configuration/config_documentation.html
+++ b/develop/usage/configuration/config_documentation.html
@@ -3480,6 +3480,16 @@ normally or via a kick or ban. Defaults to false.</p>
 <pre><code class="language-yaml">forget_rooms_on_leave: false
 </code></pre>
 <hr />
+<h3 id="exclude_rooms_from_sync"><a class="header" href="#exclude_rooms_from_sync"><code>exclude_rooms_from_sync</code></a></h3>
+<p>A list of rooms to exclude from sync responses. This is useful for server
+administrators wishing to group users into a room without these users being able
+to see it from their client.</p>
+<p>By default, no room is excluded.</p>
+<p>Example configuration:</p>
+<pre><code class="language-yaml">exclude_rooms_from_sync:
+    - !foo:example.com
+</code></pre>
+<hr />
 <h2 id="opentracing"><a class="header" href="#opentracing">Opentracing</a></h2>
 <p>Configuration options related to Opentracing support.</p>
 <hr />
-- 
cgit 1.5.1