ContextQMD
Back to Zulip

Move content to another channel

starlight_help/src/content/docs/move-content-to-another-channel.mdx

12.03.7 KB
Original Source

import FlattenedSteps from "../../components/FlattenedSteps.astro"; import ZulipNote from "../../components/ZulipNote.astro"; import MessageActionsMenu from "../include/_MessageActionsMenu.mdx"; import TopicActions from "../include/_TopicActions.mdx";

Zulip makes it possible to move messages, or an entire topic, to another channel. Organization administrators can configure who can move messages between channels.

To help others find moved content, you can have Notification Bot send automated notices to the source topic, the destination topic, or both. These notices 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 channel

<FlattenedSteps> <TopicActions />
  1. Select Move topic. If you do not see this option, you do not have permission to move this topic.
  2. Select the destination channel for the topic from the channels dropdown list.
  3. (optional) Change the topic name.
  4. Toggle whether automated notices should be sent.
  5. Click Confirm to move the topic to another channel. </FlattenedSteps>
<ZulipNote> **Note**: When a topic is moved to a private channel with protected history, messages in the topic will be visible to all the subscribers. </ZulipNote>

Move messages to another channel

<FlattenedSteps> <MessageActionsMenu />
  1. Select Move messages. If you do not see this option, you do not have permission to move this message.
  2. Select the destination channel from the channels dropdown list. If the channel input is disabled, you do not have permission to move this message to a different channel.
  3. (optional) Change the topic name.
  4. From the dropdown menu, select which messages to move.
  5. Toggle whether automated notices should be sent.
  6. Click Confirm to move the selected content to another channel. </FlattenedSteps>
<ZulipNote> **Note**: You cannot edit content of a message while changing its channel. </ZulipNote>

Moving content to private channels

Access to messages moved to another channel will immediately be controlled by the access policies for the destination channel. Content moved to a private channel will thus appear to be deleted to users who are not subscribers of the destination channel.

Content moved to a private channel with protected history will only be accessible to users who both:

  • Were subscribed to the original channel when the content was sent.
  • Are subscribed to the destination channel when the content is moved.

Moving content out of private channels

In private channels with protected history, Zulip determines whether to treat the entire topic as moved using the access permissions of the user requesting the topic move. This means that the automated notices sent by Notification Bot will report that the entire topic was moved if the requesting user moved every message in the topic that they can access, regardless of whether older messages exist that they cannot access.

Similarly, muted topics will be migrated to the new channel and topic if the requesting user moved every message in the topic that they can access.

This model ensures that the topic editing feature cannot be abused to determine any information about the existence of messages or topics that one does not have permission to access.