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

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

Moved connections and automations remain linked to their configured accounts and capabilities. 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.

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. For example, a private thread stays limited to its participants.

Merge a Space

1. Open Space settings → Danger zone in the Space you want to move.
2. Choose Merge Space.
3. Select the destination Space.
4. Choose where the source Space’s unassigned Threads should go.
5. Review the destination’s members, visibility, connections, and automations, then confirm.

Caution

A merge cannot be undone. Check the source, destination, access rules, connections, and automations before you confirm.