From 1ec31fd7054bacc16cc479d55646e56c438b8582 Mon Sep 17 00:00:00 2001 From: anoadragon453 Date: Wed, 28 Sep 2022 14:14:29 +0000 Subject: deploy: 25c0e693924ddc5234ebb15cdfdc82b553a4b2c6 --- develop/usage/configuration/config_documentation.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (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 8db17f9cec..85429d8028 100644 --- a/develop/usage/configuration/config_documentation.html +++ b/develop/usage/configuration/config_documentation.html @@ -1965,6 +1965,8 @@ as a publicly joinable room when the first user registers for the homeserver. If the room already exists, make certain it is a publicly joinable room, i.e. the join rule of the room must be set to 'public'. You can find more options relating to auto-joining rooms below.

+

As Spaces are just rooms under the hood, Space aliases may also be +used.

Example configuration:

auto_join_rooms:
   - "#exampleroom:example.com"
@@ -1974,7 +1976,7 @@ relating to auto-joining rooms below.

autocreate_auto_join_rooms

Where auto_join_rooms are specified, setting this flag ensures that the rooms exist by creating them when the first user on the -homeserver registers.

+homeserver registers. This option will not create Spaces.

By default the auto-created rooms are publicly joinable from any federated server. Use the autocreate_auto_join_rooms_federated and autocreate_auto_join_room_preset settings to customise this behaviour.

@@ -1986,7 +1988,7 @@ users cannot be auto-joined since they do not exist.


autocreate_auto_join_rooms_federated

-

Whether the rooms listen in auto_join_rooms that are auto-created are available +

Whether the rooms listed in auto_join_rooms that are auto-created are available via federation. Only has an effect if autocreate_auto_join_rooms is true.

Note that whether a room is federated cannot be modified after creation.

-- cgit 1.5.1