From b10b0dc01a50ebcbacf49ac5bcbc2d5d7f816d9c Mon Sep 17 00:00:00 2001
From: anoadragon453
Date: Thu, 12 May 2022 10:42:11 +0000
Subject: deploy: de1e599b9defdc9b541f14a03157f614cb688729
---
.../usage/configuration/config_documentation.html | 19 ++++++++++++
.../configuration/homeserver_sample_config.html | 34 ++++++++++++++++++++++
2 files changed, 53 insertions(+)
(limited to 'develop/usage/configuration')
diff --git a/develop/usage/configuration/config_documentation.html b/develop/usage/configuration/config_documentation.html
index a16cd961f0..ab92ac22ce 100644
--- a/develop/usage/configuration/config_documentation.html
+++ b/develop/usage/configuration/config_documentation.html
@@ -2968,6 +2968,25 @@ can publish rooms.
action: allow
+Config option: default_power_level_content_override
+The default_power_level_content_override
option controls the default power
+levels for rooms.
+Useful if you know that your users need special permissions in rooms
+that they create (e.g. to send particular types of state events without
+needing an elevated power level). This takes the same shape as the
+power_level_content_override
parameter in the /createRoom API, but
+is applied before that parameter.
+Note that each key provided inside a preset (for example events
in the example
+below) will overwrite all existing defaults inside that key. So in the example
+below, newly-created private_chat rooms will have no rules for any event types
+except com.example.foo
.
+Example configuration:
+default_power_level_content_override:
+ private_chat: { "events": { "com.example.foo" : 0 } }
+ trusted_private_chat: null
+ public_chat: null
+
+
Configuration options related to Opentracing support.
diff --git a/develop/usage/configuration/homeserver_sample_config.html b/develop/usage/configuration/homeserver_sample_config.html
index fe8852586e..b412f1caa3 100644
--- a/develop/usage/configuration/homeserver_sample_config.html
+++ b/develop/usage/configuration/homeserver_sample_config.html
@@ -2624,6 +2624,40 @@ push:
#
#encryption_enabled_by_default_for_room_type: invite
+# Override the default power levels for rooms created on this server, per
+# room creation preset.
+#
+# The appropriate dictionary for the room preset will be applied on top
+# of the existing power levels content.
+#
+# Useful if you know that your users need special permissions in rooms
+# that they create (e.g. to send particular types of state events without
+# needing an elevated power level). This takes the same shape as the
+# `power_level_content_override` parameter in the /createRoom API, but
+# is applied before that parameter.
+#
+# Valid keys are some or all of `private_chat`, `trusted_private_chat`
+# and `public_chat`. Inside each of those should be any of the
+# properties allowed in `power_level_content_override` in the
+# /createRoom API. If any property is missing, its default value will
+# continue to be used. If any property is present, it will overwrite
+# the existing default completely (so if the `events` property exists,
+# the default event power levels will be ignored).
+#
+#default_power_level_content_override:
+# private_chat:
+# "events":
+# "com.example.myeventtype" : 0
+# "m.room.avatar": 50
+# "m.room.canonical_alias": 50
+# "m.room.encryption": 100
+# "m.room.history_visibility": 100
+# "m.room.name": 50
+# "m.room.power_levels": 100
+# "m.room.server_acl": 100
+# "m.room.tombstone": 100
+# "events_default": 1
+
# Uncomment to allow non-server-admin users to create groups on this server
#
--
cgit 1.5.1