help center: Explain details of content moves.

This commit is contained in:
Alya Abbott
2022-03-22 17:12:22 -07:00
committed by Tim Abbott
parent 6087f0daf1
commit c121bec188
2 changed files with 18 additions and 0 deletions

View File

@@ -79,6 +79,18 @@ option.
{end_tabs} {end_tabs}
## Moving content to private streams
Access to messages moved to another stream will immediately be controlled by the
access policies for the destination stream. Content moved to a private stream will
thus appear to be deleted to users who are not subscribers of the destination stream.
Content moved to a [private stream with protected history](/help/stream-permissions)
will only be accessible to users who both:
* Were subscribed to the *original* stream when the content was *sent*.
* Are subscribed to the *destination* stream when the content is *moved*.
## Related articles ## Related articles
* [Rename a topic](/help/rename-a-topic) * [Rename a topic](/help/rename-a-topic)

View File

@@ -4,6 +4,12 @@ By default, any user can change the topic of any message. This is useful for
keeping messages organized even if some users are still learning how to use keeping messages organized even if some users are still learning how to use
topics effectively. topics effectively.
Zulip's [permanent links to messages in
context](/help/link-to-a-message-or-conversation#get-a-link-to-a-specific-message)
will automatically redirect to the new location of the message. [Muted
topics](/help/mute-a-topic) are automatically migrated when all messages
after a certain point are moved or an entire topic is renamed.
Organization administrators can Organization administrators can
[configure who can edit topics](/help/configure-who-can-edit-topics), or turn off [configure who can edit topics](/help/configure-who-can-edit-topics), or turn off
message editing entirely. See the message editing entirely. See the