--- title: How to set up a campaign url: https://tideswell.xyz/docs/projects/set-up-a-campaign description: A campaign spans teams and holds the projects working towards one date. Create one, then attach projects to it. --- > Documentation index: fetch https://tideswell.xyz/llms.txt to discover every page before exploring further. # How to set up a campaign A **campaign** is the top level of planning: a named, dated thing that projects in different teams point at. Autumn drop, Black Friday, the spring wholesale season. For where it sits relative to projects and tasks, read first. ## Before you start [#before-you-start] Creating and editing campaigns is an admin job in most workspaces, a step above projects. That is on purpose, because a campaign is workspace-wide and a project belongs to one team. If **Campaign** is absent from your **Create** menu, that is the reason. ## How do you create one? [#how-do-you-create-one] **Create** next to your workspace name, then **Campaign**. The **New campaign** dialog asks for a **Campaign name**, a **Start** date and a **Target** date. You can also create one without leaving what you are doing, from the **Campaign** picker on any project's Properties card. That is usually how the first one gets made. ## How do you put projects under it? [#how-do-you-put-projects-under-it] From the project rather than from the campaign. Open the project's **Overview** and set **Campaign** on its Properties card. A project belongs to at most one campaign, and the picker reads **No campaign** when it is empty. You can also set it while creating a project, in the **New project** dialog. See . ## Where do you see a campaign? [#where-do-you-see-a-campaign] A campaign has no page of its own. It shows up in four places, each answering a different question: * As a **band** across the roadmap, with its projects nested under it. This is the main one. * As a blue **megaphone marker** on its target date on the company calendar. * As a **property** on each project that points at it. * In the **breadcrumb** at the top of any task inside one of those projects, reading department, project, campaign. That last one is quietly the most useful. Somebody looking at a single task can see what launch it belongs to without going anywhere. ## How do you see everything happening in one campaign? [#how-do-you-see-everything-happening-in-one-campaign] Open the **roadmap** and set the grouping to **Campaign**, then use the campaign filter in the header to narrow to one. You get every project under it as a bar, with its milestones as diamonds and a **Today** line down the chart. That is the closest thing to a campaign page, and it is covered in . ## How do you change a campaign's dates? [#how-do-you-change-a-campaigns-dates] Drag its band on the roadmap, which moves the start and target together, or edit the dates directly. Dragging a band is an admin action, the same as creating one. Somebody without that right sees the band and cannot move it. ## When is a cycle the better fit? [#when-is-a-cycle-the-better-fit] When you want a repeating time-box rather than a named piece of work. A campaign is a thing with a launch date that ends when it ships. A cycle is a fortnight, and next fortnight there is another one. They coexist: a task can be in the Autumn drop campaign by way of its project, and in this fortnight's cycle at the same time. See .