# Move Campaign members without losing their history

**Date:** 2026-11-09 | **Period:** Week of November 9, 2026 | **Edition:** weekly | **Canonical URL:** https://outcomet.app/changelog/2026-11-09-move-campaign-members-without-losing-their-history

Campaign work now travels across the App, connected AI clients and Slack without dropping the context already collected around a contact. Members can move between Campaigns, duplicate enrollments merge instead of multiplying, and ownership or assignment changes can cover a selected group or the whole Campaign. Connected clients also reach further into Strategy, Discovery, Initiatives and Decisions.

## Move Campaign members, not fragments

The Campaign transfer now covers the parts that used to make a move risky:

- Move one or several members into another Campaign.
- Keep their selection rationale, fit snapshot, stage history and logged outreach touchpoints.
- Combine memberships when the contact is already enrolled in the destination, instead of creating another copy.

The Campaign Pipeline table makes selection easier to see, keeps Company and Contact fit together, and gives the next action more room. Campaign header signals now sit beside the goal, while compact, standard and large signal cards remain distinct across workspace views.

This transfer is available in the App and connected AI clients. The coordinated production rollout completed on November 13.

## Set ownership and assignments together

Campaign owners can be set or cleared from connected AI clients. The same update can assign existing members to that owner, while member assignments can also be changed for a selected group or the entire Campaign.

Workspace members can be selected by their usual account identity. Production verification completed on November 14.

## Do more product work from connected clients

Connected AI clients can now read and update more of Product Context, Strategy, Discovery, Initiatives and Decisions. Product Context can be requested in a focused shape, and Wardley Map placement is available alongside the Capability context needed to read it.

Slack members and Admins can use the supported write actions for Campaigns, Contacts, Companies, Competitors and Work Items. Viewers remain read-only. These additions reached the production MCP and Slack connectors on November 10.

## See Slack presence and keep Signal capture tidy

Bridge now shows the Slack channels and active surfaces for each Crew member, with a direct route to manage the connection. Settings shows the connected workspace, capture emoji, Nexus feed channel, activation state and joined channels for Nova, Polaris, Vega and Nexus.

Connected clients can also avoid duplicate Signals from the same source, find a Signal by its source link and open the Feedback queue that is ready for Problem review. These changes were released with the production Slack connector cutover on November 9.
