Skip to content
Type Type Type Help
Changelog

Report a bug

Merge Spaces

Workspace owners and admins can merge one Space into another. This is useful when duplicate Spaces grew around the same team or when a project should become part of a larger home.

What moves

Section titled “What moves”

The source Space’s threads, channels, skills, connections, automations, connected sources, and artifacts other than Space Instructions move into the destination Space. The source Space is archived when the merge finishes.

Moved connections remain linked to their configured accounts. Because the destination Space’s members and visibility apply, the merge can change who can use the resources and actions those credentials authorize.

For conversations in the source Space’s default Threads area, choose whether to:

  • Move them into the destination Space’s Threads area.
  • Create a new named channel for them in the destination Space.

Instructions and the default AI

Section titled “Instructions and the default AI”

The source Space’s Space Instructions do not move or combine with the destination’s instructions. Before merging, review both sets of instructions and copy any guidance you want to keep into the destination Space’s instructions. Resolve conflicting guidance before continuing.

The destination keeps its default AI. Automations using the source Space’s default AI switch to the destination’s default AI when they are attached only to the source Space, or to the source and destination Spaces. Automations also attached to another Space keep their configured agent.

Before merging, review the destination’s instructions and default AI alongside the affected automations. Afterward, check those automations in the destination Space and use Test to check their output. A test executes actions as the person testing, so review the prompt first and also check the next scheduled run. See Scheduled Automations for testing and run history.

Access after the merge

Section titled “Access after the merge”

The destination Space’s visibility and permissions apply to all moved work, including connections and automations. Review this change carefully because it can give destination Space members access to connected resources and automation actions they could not use in the source Space. If the destination is private, you must already be a member to merge into it.

Individual items can still have narrower sharing. Moving a private thread does not publish it.

Merge a Space

Section titled “Merge a Space”
  1. Review the source Space’s instructions and copy any guidance you want to retain into the destination Space.
  2. Open Space settings → Danger zone in the Space you want to move.
  3. Choose Merge Spaces and select the Destination Space.
  4. Under Where should Threads outside channels go?, choose Create a new channel and enter a name, or choose Add to Threads in the destination Space.
  5. Check the destination’s members, visibility, connections, default AI, and automations, then choose Review merge.
  6. Type the requested confirmation, such as Merge Marketing, and choose Merge followed by the source Space’s name.