Campaigns 5 min

Create a Multi-Workspace Campaign

Set up a time-bound campaign shell, attach workspace targets, and prepare for shared strategy and per-brand execution.

Overview

Creating a campaign starts with a company-scoped container and one or more targets—workspaces (brands or clients) that will receive adapted briefs in their own calendars. The campaign record holds metadata you need across the lifecycle: name, description, start and end dates, status, optional calendar policy hints, and links to the communication strategy, source documents, plan, and generated briefs.

Each CampaignTarget connects the campaign to a workspace. When you generate strategy later, CntX creates a child ContentStrategy inside each target workspace, linked to a common parent strategy shared across the campaign. That architecture lets you maintain one set of objectives and key messages while enabling local products, audiences, pillars, content types, channels, and editorial destinations per brand.

Campaign creation is intentionally lightweight. You are not configuring the full plan at this step—you are declaring who participates, when the initiative runs, and where downstream generation should write briefs. Documents, strategy tabs, and plan generation follow in subsequent steps once targets exist.

When to use

Create a multi-workspace campaign when:

  • A initiative spans more than one brand or client workspace under the same company.
  • You need a single place to attach source documents and track generation status across workspaces.
  • Marketing ops or an agency must coordinate launches without duplicating strategy objects in each workspace manually.
  • Home recommends campaign setup or you are moving from context readiness into time-bound planning.

Use a single-workspace campaign when only one brand is involved but you still want document grounding, plan slots, and Quick Review—or stay with evergreen content strategy if the work is ongoing rather than bounded.

Before you start

  • Confirm workspaces exist for each participating brand. Create or switch workspaces first if you are onboarding new properties.
  • Decide campaign name and date range. End dates help capacity planning and prevent generation from spilling indefinitely.
  • Identify a primary workspace mentally—even though targets are peers, generation orchestration processes weeks and workspaces in a stable order, and your team may review the primary calendar first.
  • Align on who approves briefs in each workspace; targets without active editors stall after generation.
  • Have company context populated in each workspace (products, audiences, brand basics) so child strategy bootstrap does not produce empty shells.

Steps

  1. Open Campaigns from the sidebar and choose Create campaign (wording may appear as New campaign depending on locale).
  2. Enter a clear name—include quarter, product, or event so future you can distinguish it from evergreen strategies.
  3. Add an optional description for internal stakeholders: objective, offer, regions, or constraints generation should respect.
  4. Set start date and end date to bound the initiative. Match real launch windows; overly long windows inflate plan size and review load.
  5. Save or continue to the targets step depending on UI flow. Targets define which workspaces participate.
  6. Select workspaces to attach as targets. Each selection will later receive its own child strategy tab and calendar briefs. Remove mistaken targets before generating strategy—cleanup is possible but easier to get right upfront.
  7. Review target list for coverage: every brand that must publish campaign content should appear; do not assume briefs copy automatically to untargeted workspaces.
  8. Confirm calendar policy or capacity mode if exposed in your build—some campaigns count against editorial cadence (included), others stack additively. When unsure, ask your admin; defaults affect conflict warnings later.
  9. Save the campaign and land on campaign detail. Note the guided steps—typically Documents → Strategy → Plan → Review—and proceed when targets show as connected workspaces with pending strategy state.

Expected result

A Campaign record exists with stable ID, date range, and CampaignTarget rows pointing at each participating workspace. Campaign detail shows targets, empty or in-progress strategy state, and entry points for document upload, strategy editor, and later plan generation.

No briefs exist yet—that is expected. Child ContentStrategy records appear after you run Generate strategy in the strategy step. Each target workspace will eventually show campaign-tagged items in its calendar once plan generation completes.

Tips / common issues

  • Missing workspace in picker — Workspace may not be provisioned under the company, or you lack access. Check Create and Switch Workspaces and permissions.
  • Wrong date range — End before start blocks generation. Fix dates before strategy snapshot.
  • Target added late — You can add targets after creation, but run strategy generation again so child strategies and channels bootstrap for the new workspace.
  • Duplicate campaigns — Two campaigns with overlapping dates and targets flood Quick Review. Archive or pause obsolete campaigns.
  • Single brand selected — Valid for document-grounded launches; you still get campaign plan mechanics without multi-tab strategy complexity.
  • Context-empty workspace — Child strategy bootstrap pulls products and audiences from workspace context. Run Complete Context Discovery or manual setup per brand first.

Next step

Add Source Documents to a Campaign if you have messaging decks or research to ground strategy—or go directly to Generate and Edit a Campaign Strategy when documents are not needed yet.

Ready to try this in CntX?

Open the product and apply this guide to your workspace.