matrix-spec-proposals/specification/modules/history_visibility.rst

Room History Visibility
-----------------------

.. _module:history-visibility:

Whether a member of a room can see the events that happened in a room from
before they joined the room is controlled by the ``history_visibility`` key
of the ``m.room.history_visibility`` state event. The valid values for
``history_visibility`` are:

- ``shared``
- ``invited``
- ``joined``

By default if no ``history_visibility`` is set it is assumed to be ``shared``.

The rules governing whether a user is allowed to see an event depend solely on
the state of the room at that event:

1. If the user was joined, allow.
2. If the user was invited and the ``history_visibility`` was set to
   ``invited`` or ``shared``, allow.
3. If the user was neither invited nor joined but the ``history_visibility``
   was set to ``shared``, allow.
4. Otherwise, deny.
Document m.room.history_visibility 9 years ago			`Room History Visibility`
Modify and enforce the file format/structure used Convert the file format to be of the form ##_##_something.rst where the first ## is the top-level section number and the second ## is the second-level section number, e.g. 07_01_push_cs_api.rst means Section 7.1 - This is now enforced in gendoc.py along with the title line style that should be used (= for top-level, - for 2nd level) which will give helpful suggestions if you trip up. This feels much more intuitive now looking in /specification 9 years ago			`-----------------------`
Document m.room.history_visibility 9 years ago
Add room history visibility as a module. 9 years ago			`.. _module:history-visibility:`

Make it clearer 9 years ago			`Whether a member of a room can see the events that happened in a room from`
			before they joined the room is controlled by the ``history_visibility`` key
			of the ``m.room.history_visibility`` state event. The valid values for
			``history_visibility`` are:
Document m.room.history_visibility 9 years ago
			- ``shared``
			- ``invited``
			- ``joined``

Make it clearer 9 years ago			By default if no ``history_visibility`` is set it is assumed to be ``shared``.
Document m.room.history_visibility 9 years ago
			`The rules governing whether a user is allowed to see an event depend solely on`
Make it clearer 9 years ago			`the state of the room at that event:`
Document m.room.history_visibility 9 years ago
			`1. If the user was joined, allow.`
			2. If the user was invited and the ``history_visibility`` was set to
			``invited`` or ``shared``, allow.
			3. If the user was neither invited nor joined but the ``history_visibility``
			was set to ``shared``, allow.
			`4. Otherwise, deny.`