Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/help/move-content-to-another-str...

2.7 KiB
Raw Blame History

Move content to another stream

Zulip makes it possible to move messages or an entire topic to another stream. Organizations can configure which roles have permission to move messages between streams.

To help others find moved content, you can have Zulip send automated notification messages to the source topic, the destination topic, or both. These notifications include:

  • A link to the source or destination topic.
  • How many messages were moved, or whether the whole topic was moved.
  • Who moved the content.

Move a topic to another stream

To move a topic, you must have access to both the source and destination streams.

{start_tabs}

{!topic-actions.md!}

  1. Select Move topic.

  2. Select the destination stream for the topic from the streams dropdown list.

  3. (optional) Change the topic.

  4. Toggle whether automated notification messages should be sent.

  5. Click Confirm.

!!! warn ""

**Note**: When a topic is moved to a private stream with protected history,
          messages in the topic will be visible to all the subscribers.

{end_tabs}

Move messages to another stream

{start_tabs}

{!message-actions-menu.md!}

  1. Select the first option. It may be called View source / Move message, or simply Edit. If it's called View source, then you are not allowed to edit the stream of that message.

  2. Select the destination stream for the message from the streams dropdown list.

  3. (optional) Change the topic.

  4. Toggle whether automated notification messages should be sent.

  5. From the dropdown menu, select which messages to move:

{!move-content-subset-options.md!}

  1. Click Save.

!!! warn ""

**Note**: You cannot edit content of a message while changing its stream.

{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 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