summary refs log tree commit diff
diff options
context:
space:
mode:
authorKegan Dougal <kegan@matrix.org>2014-09-02 21:45:36 +0100
committerKegan Dougal <kegan@matrix.org>2014-09-02 21:45:36 +0100
commit70aa4b9231d8b1412fbff91a83d31a468c5d7d87 (patch)
tree7aafebc8e537bcfa98f60fcd7b2291f1f3c1b76a
parentAdded Qs which should be answered in the marked TODOs (diff)
downloadsynapse-70aa4b9231d8b1412fbff91a83d31a468c5d7d87.tar.xz
Edited room creation section to mention all the events created when the room is.
Diffstat (limited to '')
-rw-r--r--docs/specification.rst17
1 files changed, 16 insertions, 1 deletions
diff --git a/docs/specification.rst b/docs/specification.rst
index 07b57ef2ab..20e7a0d85f 100644
--- a/docs/specification.rst
+++ b/docs/specification.rst
@@ -351,7 +351,6 @@ Rooms
 Creation
 --------
 .. TODO kegan
-  - TODO: This creates a room creation event which serves as the root of the PDU graph for this room.
   - TODO: Key for invite these users?
   
 To create a room, a client has to use the |createRoom|_ API. There are various options
@@ -412,6 +411,22 @@ Example::
     "topic": "All about happy hour"
   }
 
+The home server will create a ``m.room.create`` event when the room is
+created, which serves as the root of the PDU graph for this room. This
+event also has a ``creator`` key which contains the user ID of the room
+creator. It will also generate several other events in order to manage
+permissions in this room. This includes:
+
+ - ``m.room.power_levels`` : Sets the authority of the room creator.
+ - ``m.room.join_rules`` : Whether the room is "invite-only" or not.
+ - ``m.room.add_state_level``
+ - ``m.room.send_event_level`` : The power level required in order to
+   send a message in this room.
+ - ``m.room.ops_level`` : The power level required in order to kick or
+   ban a user from the room.
+
+See `Room Events`_ for more information on these events.
+
 Modifying aliases
 -----------------
 .. NOTE::