deploy: de1e599b9d
This commit is contained in:
@@ -2968,6 +2968,25 @@ can publish rooms.</p>
|
||||
action: allow
|
||||
</code></pre>
|
||||
<hr />
|
||||
<p>Config option: <code>default_power_level_content_override</code></p>
|
||||
<p>The <code>default_power_level_content_override</code> option controls the default power
|
||||
levels for rooms.</p>
|
||||
<p>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
|
||||
<code>power_level_content_override</code> parameter in the /createRoom API, but
|
||||
is applied before that parameter.</p>
|
||||
<p>Note that each key provided inside a preset (for example <code>events</code> 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 <code>com.example.foo</code>.</p>
|
||||
<p>Example configuration:</p>
|
||||
<pre><code class="language-yaml">default_power_level_content_override:
|
||||
private_chat: { "events": { "com.example.foo" : 0 } }
|
||||
trusted_private_chat: null
|
||||
public_chat: null
|
||||
</code></pre>
|
||||
<hr />
|
||||
<h2 id="opentracing"><a class="header" href="#opentracing">Opentracing</a></h2>
|
||||
<p>Configuration options related to Opentracing support.</p>
|
||||
<hr />
|
||||
|
||||
Reference in New Issue
Block a user