Clarify what happens when there is no power_levels event

This commit is contained in:
Richard van der Hoff 2017-10-17 16:34:50 +01:00
parent 1afe02d07d
commit b4e24d443a
3 changed files with 16 additions and 1 deletions

View file

@ -37,6 +37,9 @@ paths:
the new room, including checking power levels for each event. It MUST the new room, including checking power levels for each event. It MUST
apply the events implied by the request in the following order: apply the events implied by the request in the following order:
0. A default ``m.room.power_levels`` event, giving the room creator
(and not other members) permission to send state events.
1. Events set by ``presets``. 1. Events set by ``presets``.
2. Events listed in ``initial_state``, in the order that they are 2. Events listed in ``initial_state``, in the order that they are

View file

@ -29,6 +29,17 @@ description: |-
to 50 if they are not specified in the ``m.room.power_levels`` event, or if to 50 if they are not specified in the ``m.room.power_levels`` event, or if
the room contains no ``m.room.power_levels`` event. the room contains no ``m.room.power_levels`` event.
.. NOTE::
As noted above, in the absence of an ``m.room.power_levels`` event, the
``state_default`` is 0, and all users are considered to have power level 0.
That means that **any** member of the room can send an
``m.room.power_levels`` event, changing the permissions in the room.
Server implementations should therefore ensure that each room has an
``m.room.power_levels`` event as soon as it is created. See also the
documentation of the ``/createRoom`` API.
properties: properties:
content: content:
properties: properties:

View file

@ -9,7 +9,8 @@
{% endif -%} {% endif -%}
{{event.desc | wrap(80)}} {{event.desc}}
{% for table in event.content_fields %} {% for table in event.content_fields %}
{{"``"+table.title+"``" if table.title else "" }} {{"``"+table.title+"``" if table.title else "" }}