From b10b0dc01a50ebcbacf49ac5bcbc2d5d7f816d9c Mon Sep 17 00:00:00 2001 From: anoadragon453 Date: Thu, 12 May 2022 10:42:11 +0000 Subject: deploy: de1e599b9defdc9b541f14a03157f614cb688729 --- develop/usage/configuration/config_documentation.html | 19 +++++++++++++++++++ 1 file changed, 19 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 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
+
+

Opentracing

Configuration options related to Opentracing support.


-- cgit 1.5.1