# Create a campaign

## Purpose
Set up the container that holds a round of assessment: its people, its assessments, its
dates, and how people get in.

## Who this is for
Account administrators and campaign managers.

## Before you start
Decide two things, because they change what the rest of the setup looks like:

- **Private or public.** This decides how the campaign presents itself, not who may
  answer it. A public campaign gets the **Public Campaigns Page** settings (its public
  link, a public description, instructions and an optional document) and can be
  listed (see [List the campaign on assessor.io](#list-the-campaign-on-assessorio)). A
  private campaign is not necessarily invitation-only: with a passcode, anyone who
  knows it can answer.
- **How people prove they belong.** The campaign's **Who may answer** mode is one of
  three: anyone with the link, a shared campaign passcode, or invitation only. A
  registration form can sit alongside any of them: it is an extra door, not a fourth
  mode.

You can change all of this later in campaign **Settings**.

## Create it

1. Open the account **Dashboard** (the first sidebar item).
2. Choose **New campaign** in the top-right of the account header.
3. Fill in the dialog:
   - **Campaign Name**: required.
   - **Description**: up to 500 characters. This is an internal note; it is never
     shown to visitors. Settings adds a separate **Public description** once the
     campaign is public (see [Finish the setup](#finish-the-setup)).
   - **Status**: start in **Draft** unless you are ready for people to arrive.
   - **Public campaign**: leave unticked for a private campaign. New campaigns default
     to private.
   - **Enable registration**: on by default; it means the campaign expects applicants
     to come through a registration form.
   - **Require passcode**: reveals a passcode field when ticked. Read
     [What a campaign passcode lets people do](#what-a-campaign-passcode-lets-people-do)
     before you choose one: on a private campaign the passcode is enough to
     answer, with no account.
4. Choose **Create**.

Filled in for a private campaign that starts as a draft, the dialog looks like this:

![The New Campaign dialog with a campaign name and an internal description typed in, a character count of 88 of 500, Status set to Draft, Public campaign unticked, Enable registration ticked and Require passcode unticked, above the Cancel and Create buttons.](/assets/public_doc_images/guides/create-a-campaign-new-campaign-dialog.webp)

The campaign appears as a card on the dashboard with **Draft** / **Active** /
**Inactive** and **Private** / **Public** badges. Choose the campaign's **name** on the
card to open it; the gear icon beside it edits the campaign's properties without
leaving the dashboard.

## What a campaign passcode lets people do

On a **private** campaign, the passcode is a door into the questionnaire, not
only into the campaign. Anyone who opens `/public/campaign/<key>` and types it
can answer, there and then, with no account and no invitation. Their response is
**anonymous**: it is filed as a walk-up, exactly like a response on an open
campaign, because a passcode says that somebody knows a shared secret and does
not say who they are.

Some consequences worth knowing before you set one:

- **The passcode is as strong as you make it.** Use **Generate** rather than
  typing a phrase. A typed passcode is refused if it is shorter than **sixteen
  characters**, if it uses fewer than **six different characters**, or if its
  letters are **one or two common words**, and **Generate** mints something that
  clears all three, so the button beside the field always produces a passcode the
  field accepts. Both dialogs say all three rules beside the field before you
  type. Common words are read in **English and French**, accents and all, and one
  word of each counts as two, though the French half covers base forms rather
  than every inflection, so it catches less than the English half does. Three or more words are allowed, but a campaign
  address is not a secret at all: it appears in URLs and on posters.
- **It is shared, so it travels.** One person forwarding it hands on the same
  access they have. If you need to know who answered, invite people instead: an
  invitation mints a personal link, and only that link produces an identified
  response.
- **An address a walk-up types is a label, not a name we recognise.** Where a
  questionnaire asks for one, we record it on the new entry that response
  creates. We never match it against your roster and file the answers under the
  person who owns that address. So somebody you invited who answers as a walk-up,
  without their link, appears on the roster twice: once as invited, once as a
  walk-up carrying the same address. That is deliberate. The alternative is that
  anyone who knows a colleague's address can file answers as them, on any campaign
  that accepts walk-ups. Reports that count PEOPLE fold the two entries back into
  one; counts of roster ENTRIES show both.
- **Changing the passcode ends every sitting that is using the old one.**
  Setting a passcode, replacing it, or clearing it all count as a change.
  Anyone who typed the previous passcode is asked for the new one the next time
  they save a page, so if you rotate a passcode mid-wave, expect to hand the
  new one out to people who are already part-way through. That is what makes
  rotation worth doing when a code leaks: the old one stops working
  immediately, rather than staying good for the rest of the day.
- **Turning the passcode off does not turn the door off.** A private campaign
  with no passcode is invitation-only, which is more restrictive, not less, but
  a passcode you set and then forget stays usable until you change it.
- **A passcode set before these rules keeps working.** They apply when a
  passcode is *written*, never when one is *checked*, so an older campaign
  carrying a shorter code (or a two-word phrase) is not locked out and nobody
  has to be told to re-enter anything. You can still rename such a campaign,
  change its dates and edit everything else about it. The next time you change
  that passcode it will have to satisfy all three rules, and **Generate** is the
  fastest way there.

If none of that is what you want, leave **Require passcode** off and invite
people. If you want anyone at all to answer, make the campaign public.

## How many colleagues one respondent may bring in

On a campaign whose assessments are answered by an **organisation** or by a
**department** rather than by each person separately, anyone already taking part
can invite colleagues into the same organisation. They create a link from **My
assessments** or from the page they see after submitting, and send it on; each
person who opens it agrees to take part for themselves before anything is
recorded.

**One link is worth ten newcomers unless you say otherwise.** The number lives
on the campaign, under `shareLink.maxJoiners` in the campaign's settings, and
can be anything from **1** to **100**. A value outside that range is pulled back
into it rather than refused, so a mistyped setting never stops a respondent
inviting somebody.

Four things are worth knowing before you change it:

- **The cap is fixed when a link is created, not when it is used.** Lowering the
  number does not cut off links people are already holding, and raising it does
  not re-open a link that has already done its work. Set it before a wave rather
  than during one.
- **One person can only hold a few live links at a time.** The cap limits each
  link; this limits how many links one respondent can have outstanding. They can
  withdraw a link they no longer need to free the budget.
- **Links last thirty days**, and the person who created one can **withdraw** it
  at any time.
- **These people count as invited.** On the Engagement tab they are on the
  invited side of the funnel, not with the walk-ups, because a named colleague
  on your roster asked them, and the record says who. A passcode walk-up is
  still anonymous and still self-serve; the two are deliberately different.

**Nothing changes on a campaign whose assessments are answered by each person
individually.** There is no organisation to share, so the action is not offered
and a request for one is refused with a message saying so.

## Finish the setup

Inside the campaign, **Settings** in the header opens the fuller editor. The sections
that matter:

**Campaign Info**: display order, status, title, an internal note (never shown to visitors, see **Public description** below for the field that is), and a campaign image.

**Campaign Admin**: the Private/Public pill (which decides presentation on the public
page), **Who may answer** (*Anyone with the link* / *Passcode* / *Invitation only*, the
mode the join gate actually enforces), "Share with all account users", "Enable Passcode"
and its value, "Enable registration step", and **Contact address for respondents**.
Read [Who a stuck respondent writes to](#who-a-stuck-respondent-writes-to) before you
fill that last one in: the address is published.

**Campaign consent**: off until you configure it, including on every campaign that
already existed when this setting was added. Turning it on makes the campaign, rather
than each questionnaire template, own the consent statement. The study owner supplies
and approves all three required values: the English wording, the French wording, and a
version identifier. Use a new identifier whenever the approved wording changes. The
identifier is stored with the response for audit but is never shown to a participant.

The wording is rich text: one **Approved consent text** editor with **English** and
**French** tabs. Its toolbar sets the text style (**Paragraph**, **Heading** or
**Subheading**), bold, italics, bulleted lists and links (an address starting with
`https://`, `http://` or `mailto:`, or a path on this site), and the `<>` button (**Edit HTML**)
shows the HTML itself. Formatting the editor does not support is removed when you switch back
from the HTML, and the editor says so. Participants see the formatting on the consent
page, and links open in a new tab. Wording written before the editor existed keeps its
paragraphs, and opening and saving a campaign without changing the words changes nothing
that is stored. Editing the wording does not change the version identifier: that stays
yours to update.

**Allow consent per assessment** decides what a refusal closes:

- Off: consent is asked before the participant's first assessment. A refusal closes
  the campaign for that participant, so its other assessments disappear from their
  open list.
- On: a refusal closes only the assessment in front of them; the campaign's other
  assessments remain open. An individual assessment can also enable **Ask for consent
  again inside this assessment** in its own editor. That assessment-level switch is
  unavailable until campaign consent and **Allow consent per assessment** are both on.

An agreement to the current version is reused across the campaign unless an assessment
is set to ask again. Publishing a new version asks again because the earlier agreement
names different wording.

**Terms and privacy**: this campaign's own **Privacy statement** and **Conditions of
taking part**, each in English and French. Leave a text empty to use the account's
text from **Settings > Legal**: the section links there and can show you the account's
text, read only, so you know what an empty field gives participants. When only the
English text is set, French readers see that English text rather than the account's.
Use this when one campaign runs under different terms from the rest of the account, for
example a study with its own privacy notice. These texts are what participants see on the campaign's public
page, its application form, the welcome page, the questionnaire and a share link's page,
and an agreement is recorded against the text the person was shown (see
[Give respondents your own terms and privacy statement](/operate/tenant-admin/account-legal-text)).

**Embedding**: which websites may show this campaign's assessments inside their own
pages, and how long responses are kept. See
[Embedding, and how long responses are kept](#embedding-and-how-long-responses-are-kept).

**Campaign Lifecycle**: up to ten open/close windows, each with an *Opens* and a
*Closes* timestamp. Use these when a campaign runs in rounds.

**Public Campaigns Page**: only shown when the campaign is public. It gives you the
public URL with a copy button, the **Public link** field that sets it (see
[The campaign's public link](#the-campaigns-public-link)), and a **Public description**
field: up to 500 characters, shown under the campaign's name on the public page itself.
It is separate from the internal note in **Campaign Info**: leaving it empty shows no
blurb rather than falling back to that internal text, so a coordinator's own working
notes never reach an anonymous visitor. Below it are three rich-text editors,
opened from **Edit Campaign
Instructions**, **Add 'Campaign Closed' Message** and **Add 'Campaign Archived'
Message**. The two messages are
what visitors see once the campaign stops accepting responses. You can also attach a
custom document (PDF or DOCX) and choose whether the public page shows the participant
count and download count.

**Reminders and follow-ups**: three settings that apply to every reminder this
campaign sends. **Skip window (hours):** is how long after a reminder the same person
is skipped. **Repeat-request window (hours):** stops a double-clicked button mailing
everyone twice. **Let one reminder mention optional assessments**, off by default,
lets each person be told once about optional assessments, which are otherwise never
chased. Sending reminders is covered in
[Add people to a campaign](/operate/tenant-admin/add-people-to-a-campaign#message-the-group).

**Contact person**: assign one or more members as the campaign's named contacts. This
is an internal assignment; it is not the address in the next section, and it is never
shown to a respondent.

Choose **Update** to save.

## The campaign's public link

A public campaign is reachable at a page anyone can open. **Public link**, in the
**Public Campaigns Page** section, is the part of that address you choose. Leave it
empty and the campaign keeps its dashboard link; fill it in and the campaign answers at
`/public/campaign/<your link>`, the same address campaign invitation emails point at.
The **Public URL** row above the field always shows the whole thing, with a copy button.

**What you type is tidied before it is saved.** The link is lower-cased, trimmed, and
any slashes at the very start or end are dropped, so `/Wave-A/` and `wave-a` are the
same link, and typing either stores `wave-a`. The field shows you the result under the
box (*Stored and matched as …*) and the **Public URL** row above it updates to match, so
what you copy from that row is what visitors will reach.

**It has to be free, and the field checks while you type.** Public links are unique
across the whole platform, not just your account, so a link may already belong to a
campaign you cannot see. A moment after you stop typing the field says whether the link
is free, taken, or not a usable link at all, and **Update** stays disabled until it is a
link you can have. It never tells you whose campaign holds a taken link.

**What makes a usable link:** 3 to 200 characters, starting with a letter or digit, and
made of letters, digits and `- _ . : / ~ +`. No spaces, no `?`, no `#`. A full
`https://…` address is accepted too, for a campaign you host somewhere else.

**Changing it breaks the old address.** Anything already handed out (a printed slide, a
QR code, an email) stops resolving the moment you save the new link. Clearing the field
does the same. Nothing redirects from the old link to the new one.

## List the campaign on assessor.io

**List on assessor.io**, in the **Public Campaigns Page** section, puts the campaign on
the assessor.io home page, under *Open now to all*. Visitors see a card with its logo,
its name, who it is for, how to join, the languages it runs in and when it closes, and
an **Open** button that goes to its public link. The same card also appears on the
**public campaigns page** (`/public/campaigns`, linked from the home page as **See
all**), where visitors can search every listed campaign and filter by how to join
and by language. It is **off by default**: nothing appears on either page unless someone
on your account switches it on.

**A listed campaign shows only while it is open.** It needs all of these at once: the
switch on, a public link, a public page (the campaign is not Private), the campaign
Active and inside its open-and-close dates, and your account active. When it closes it
drops off by itself; a change you save shows on the home page within a few minutes.

**Listing also lets search engines show the campaign's page.** On the same conditions
apart from the dates, a listed campaign's page may appear in search results: before it
opens and after it closes, as well as while it is open. If your account runs in English
and French, search engines are told about both versions. Every campaign page that is not
listed asks search engines to leave it out, so a link you send only to the people you
invite stays out of their results even if someone posts it elsewhere. Search engines
notice a change in their own time, so a campaign you stop listing can stay in their
results for a while.

**Any way of joining can be listed.** The card says how people get in (open to all, an
access code, by invitation, or by application), so listing an invitation-only campaign
advertises it without letting in anyone you did not invite.

**Who it's for** is an optional single line shown on the card, such as *Asset owners*
or *Students and graduates*: plain text, up to 80 characters. Leave it empty and the
card shows only how to join and the languages.

**A copied campaign starts unlisted**, even when the original is listed, so a clone never
appears on the home page before you have finished setting it up.

## The welcome page and the campaign explainer

The **Welcome page** section of campaign **Settings** holds the campaign's explainer: what
you tell people about the campaign before they answer. It is on every campaign, private
ones included, because invited respondents are exactly who it is for. It is used in two
places:

- **The welcome page.** An invited respondent who opens their link sees it before the
  questionnaire: the assessment's title and *Responding as* their name at the top, the
  campaign image (if you set one) with its status (*Open until …*), up to four short
  facts (a value and a label, such as *25–30 min* and *to complete*), its own headline
  (eyebrow, heading and lead), one **Start** button that leads to the questionnaire
  (consent first) with your line beside it, and your sections as tabs. Someone who has
  already started skips it and goes straight back to their answers. Inside the
  questionnaire, **About this assessment** at the foot of the page shows the same text
  again, in tabs, without leaving it. Before the campaign opens, the page shows the
  opening date in place of **Start** and asks them to keep the invitation email.
- **The public campaign page.** Your organisation's name and how to take part
  (*By invitation*) at the top; the image and its status; its own headline; its key
  dates in date order (the opening, the close and results after, with *Now* in its
  place among them); one main button (*Participate* on an invitation-only
  campaign with a registration form, which also says "Participation is open
  until *date*"; *Take part* on a campaign anyone can join, with no second
  button); and the sections you mark for it, as tabs. Once the campaign has closed, the button gives way to *Closed on* and the
  closing date, followed by your closed notice (for example what happens to the
  results), if you wrote one. When the campaign belongs to a programme (see
  [Run the next wave](#run-the-next-wave)), **What's next** follows: the programme's
  next campaign, open or yet to open. The campaign's privacy statement and conditions of taking part (the
  account's, where the campaign has none) open from **Terms and privacy** at the foot of the page.

**Each page has its own headline.** The heading is required as soon as anything else in
that headline, or a fact, is filled in. The eyebrow and the lead are optional.

**Sections are the pages' tabs.** Each one has a short tab label (32 characters at
most), a kind (*What is involved*, *Why take part*, *How answers are used and
protected*, *Who can take part*, *How it works* with numbered steps, *Questions and
answers*, *Contact*, or *Other*) and a **Show on** choice: both pages, the welcome page
only, or the campaign page only. A section holds paragraphs and lists (one point per
line). A section with nothing in it shows no tab. Use the arrow buttons to change the
order; they work from the keyboard.

**Campaign image.** Optional: a square image (at least 600 by 600) given by its https://
address, with a description for people who cannot see it. The description is required
whenever an image is set. It is shown in a framed square beside the headline (a small
square on a phone). Without one, the pages simply leave it out: there is no empty frame.

**Plain text only.** Formatting tags are refused, and the field says so. Four
placeholders are filled in for each reader: `{organisation}` (the organisation their link
answers for, or *your organisation* on the public page), `{organiser}` (your account's
name), `{opensAt}` and `{closesAt}` (the campaign's dates, in the reader's own day).

**Contact.** *Who answers questions about taking part* and their email, and an email for
data questions and deletion requests. They are shown in a tab of their own (*Questions*
on the welcome page, *Contact* on the campaign page), or inside your *Contact* section
if you add one. The *Contact us.* link beside **Start** opens that tab.

**Saving.** Nothing changes until you press **Update**. The preview shows, as plain text,
what each page will hold. **Reset explainer** removes it all (after asking); once you
press Update, respondents go straight to the questionnaire again and the campaign page
shows only the campaign's name, description and dates. A campaign with no explainer
has no welcome page.

**Other languages.** A translation is a whole copy of the explainer in that language. It
is set through the API for now (`campaign_copy`, field `explainer`); the translation
screen does not offer it yet.

## Who a stuck respondent writes to

A respondent whose link will not open (it was mistyped, it expired, it was reissued, or
they reached a private campaign without an invitation) gets a screen explaining what
happened and telling them to ask whoever invited them. **Contact address for
respondents** is who "whoever invited them" is.

Leave it empty and nothing changes: the screen offers the platform's own contact form,
and so do the public campaign page and the campaign sign-in page for an invitation-only
campaign. Fill it in and all three offer your address instead, as a
**Contact &lt;address&gt;** link that opens the visitor's mail app.

**The address is published.** Three things follow from that, and they are the whole
reason this is optional:

- **It is shown to people who are not signed in and never will be.** All three surfaces
  that render it are public: the campaign page at `/public/campaign/<key>`, which anybody
  can open; the campaign sign-in page at `/auth/entry`, which an uninvited visitor
  reaches by following a campaign link; and the link-failure screen, which is reached
  precisely by someone with no valid credential. There is no version of this that is
  shown only to invitees.
- **Use a shared address, not a person's.** A wave inbox (`bim-survey@example.org`)
  survives someone leaving, absorbs the misdirected mail a published address attracts,
  and does not put one colleague's name on a page that may be indexed or forwarded.
- **You can take it back.** Clearing the field and choosing **Update** removes it, and
  all three surfaces revert to the platform contact form on the next page load. Nothing
  is cached anywhere else.

It has to be a valid email address; **Update** stays disabled and the field explains
itself until it is one.

## Embedding, and how long responses are kept

The **Embedding** section of **Settings** holds two settings that meet at the
anonymous respondent: which websites may show your assessments inside their own
pages, and how long the responses are kept. The developer's side of embedding (the
addresses to frame, the messages a page receives, embed tokens) is in
[Embed an assessment or its results](/build/developer/embed-an-assessment).

### Who can submit through an embed

The top of the section says where the campaign stands:

- **Anyone who opens an embedded assessment can submit**: the campaign's **Who may
  answer** is *Anyone with the link*. Each respondent becomes a new participant.
  Without an email address, every submission counts as a new participation rather than
  a new person.
- **Only people you have invited can submit**: any other **Who may answer** mode. An
  embedded assessment refuses a respondent who has no invitation, so an embed on a
  public page cannot be completed.

This is a statement, not a switch. To change it, change **Who may answer** in
**Campaign Admin**.

### Which sites may embed the campaign

Assessments in this campaign can be embedded on the sites you list here, and nowhere
else. With none listed, the section says *No sites registered: embedding is off for
this campaign.*

1. Type the site into **Website address** as a full origin: `https://` and the host,
   such as `https://www.example.com`. No path and no wildcard; a site with several
   subdomains lists each one.
2. Optionally, give it a **Channel name (optional)**, such as *Marketing site*. The
   name tags the submissions that arrive through that site.
3. Choose **Add site**, then **Update**.

Only add sites you control or trust: a listed site can show your assessment inside its
own pages. **Remove** takes a site off the list, and it stops working within a minute.
A campaign can list up to 20 sites.

### The access code

**Give anonymous respondents an access code** is on unless you turn it off. A
respondent who answered without giving an email address is shown a code once, at the
end. It is the only way they can get their answers back or have them deleted, because
nothing else ties those answers to them. People who gave an email address are not
shown one.

### How long responses are kept

Two separate periods, because they cover two different kinds of response:

- **Delete anonymous responses after (days)**: responses nobody can put a name to. On
  the date, the responses are permanently deleted and the access code stops working,
  so nobody loses the right to their answers while you still hold them. The respondent
  is shown the date beside their code.
- **Delete identified responses after (days)**: responses you can put a name to
  (someone you invited, or someone who gave an email address). Each response is
  permanently erased that many days after it was submitted, with its attachments and
  its reviewer notes. The person stays on the participant list. The erasure is the same
  one an administrator's deletion performs, so it also deletes your contact record for
  that email address, if you keep one (the hint beside the field says otherwise). The
  respondent is shown the date on the confirmation screen after they submit.

Either can be from 1 to 3,650 days. Three things follow:

- **Nothing is deleted unless you set a period.** Both fields start empty, showing
  *Never*. An empty anonymous period keeps those responses indefinitely; an empty
  identified period keeps them for the life of the account. A campaign with no period
  is never touched by the automatic deletion.
- **A period applies to responses you already hold.** Each response is measured from
  the day it was submitted. Setting or shortening a period can therefore erase older
  responses the next time the automatic deletion runs.
- **Deleted means deleted.** It cannot be undone, and files attached to a response go
  with it. Anything already exported is outside its reach.

This is different from a respondent withdrawing. Withdrawal stops their answers being
used and deletes nothing; see
[What other people can see about you](/use/participants/participant-data-visibility#stopping-deleting-and-how-long-things-are-kept)
for how the three fit together from the respondent's side.

## What happens next
- A **Draft** campaign is invisible to participants even if an assessment inside it is
  published. Set it **Active** when you are ready.
- The campaign's overview shows Active assessments, Unique participants, Total
  submissions, **Completion rate (cumulative)** and **Avg completion time**, filtered by
  the date-range, participant-status and assessment controls above them.
- **Clone** in the campaign header copies the campaign: see
  [Run the next wave](#run-the-next-wave) below, which is what it is for.

## Run the next wave

A wave **is** a campaign. There is no separate "wave" object and no "start round 2"
button: you clone the campaign you just ran, and the copy is the next wave.

**1. Clone.** *Clone* in the campaign header asks first (*Make a copy of "X"?*), with
two opt-ins, both off by default:

- **Also copy this wave's message templates.** Off, because these are the only copied
  children addressed *at* people: a reminder body written for this wave carries this
  wave's dates. Tick it if you would rather edit them than rewrite them.
- **Carry the cohort into the copy.** Off, because the same button also duplicates a
  campaign as a template to start a different programme, and that copy must not quietly
  acquire somebody else's roster. The hint tells you how many people it would copy, and
  how many units are complete in the wave you are cloning.

**2. What the copy has.** The questionnaires, their template versions, their labels,
who answers each one and whether it is mandatory; the campaign's landing copy and every
translated field; the recruitment and report targets; and the **published structure**,
with every rule pointing at the copy's own assessments. It lands as a **Draft** with
**no opening or closing dates**. Set the new wave's dates before you make it Active, or
it will run with no window.

**3. What it does not have.** No answers: submissions are never copied. No invitations:
nobody has been asked yet. Not the source's join passcode: if the original was
protected, the copy gets a **freshly minted one, shown once** in the acknowledgement
dialog. Copy it before you close that dialog; it is hashed at rest and cannot be read
back. Not the public link, which is unique and has to be minted again.

**4. If you carried the cohort.** Each person arrives with their name, organisation,
labels, language and how they first joined the programme, as **Invited**, with **no
consent recorded**: consent is taken again for every wave. Nothing they did last wave
comes across: no completion, no started date, no reminder history, no "we already told
them" flags. Two exceptions are named in the acknowledgement dialog:

- **Suspended people are left behind.** Suspending somebody was a decision about that
  person; the copy does not overrule it. Add them to the copy deliberately if this wave
  should include them.
- **A refusal or a withdrawal carries forward.** If somebody declined in the
  questionnaire, or withdrew, that stands: they are not asked again and are not counted
  as unknown. Everyone else's consent resets.

**5. Invite.** The copy has the people but has asked none of them. Send the invitations
from the copy's participants tab when the dates are set. That is also when consent is
asked again.

**6. The same person, twice.** Somebody who took the last wave may come back under a
different address: a new employer, a personal address. Two addresses are two people to
every count until you say otherwise: open them on the **Engagement** tab, use
**Same person as…** in the person dialog, name the other address and confirm. Nothing is
merged and nothing is deleted (both keep their own rows and their own answers), but
from then on every count treats them as one person, and the dialog shows a
**Linked identity** badge. You can undo it one address at a time.

The acknowledgement dialog after a clone also names the **contact address the copy
carries over** from the original, because that address is published and the new wave may
not be the old wave's to answer.

**Waves that belong together can share one address: a programme.** A programme is an
ordered series of your account's campaigns, such as the waves of a study that runs for
several years. It has one public address, `/p/<key>`, which sends visitors to its current
campaign: the open one, else the next to open, else the one that closed most recently. Put
that address in newsletters, slides and partner pages, and it keeps working after each wave
closes, where a wave's own public link would not. Once a wave has closed, its public page
names the next one under **What's next**: its name, the lead of its headline (else its
description), the date it opens if it has not opened yet, and a link to its page. A campaign belongs to one programme at most, and only a campaign that is
Active, with a public page and a public link, is ever chosen. For now the Assessor.io team
sets programmes up: ask them to create one, or to add a new wave once you have made it.

**Keep a closed wave Active.** Setting it **Inactive** replaces its public page with
*This assessment has been archived*, which does not show **What's next**.

**A programme can have a page of its own.** Instead of sending visitors on, `/p/<key>` can
show the programme itself: its name and introduction, what is open now with one button to
take part, a timeline from the first wave to the last milestone, four ways in ("My
organisation was invited", and so on), the Specialized Sets and their status, how
information is handled, common questions, and "We asked, you said, we did". It is written
in English and French, and it shows the waves' own names and dates as they stand when it
is opened. A programme starts as a **draft**, which keeps the address sending visitors on.
It moves to **unlisted** (the page, kept out of search engines, for reviewers who have the
link) and then **public** only once every word has its French. Even a public page stays out
of search engines unless that is switched on as well. For now the Assessor.io team loads
the page's text and changes these settings: send them the approved wording in both
languages.

## What each person sees: the four availability states

An assessment is not simply "in the campaign or not". Once a campaign has a
**published structure**, each assessment reads as one of four things for each
person, and which one it is can change as answers come in.

- **Mandatory**: they have to do it. It counts towards whether they are finished.
- **Optional**: they may do it. It is offered, and nobody is chased for it.
- **Locked**: it is theirs, but not yet. It depends on another assessment that
  nobody in their organisation, department or own record has finished. The
  refusal names the one that has to come first, so "not yet" never reads as "no".
- **Hidden**: it is not offered to them at all. Either a rule says so, or the
  unit that answers it has no place for them: no organisation on their record, no
  department label, two department labels at once, or a department list that has
  been deleted.

Two things follow from this that are worth knowing before you write rules.

**A campaign with no published structure behaves exactly as it always has.**
Every non-draft assessment is available and mandatory for everyone. Nothing
changes until you publish a structure.

**A locked assessment reopens the moment its source is finished, for everybody
who shares it.** If the Core Set is answered by the *organisation*, one
colleague completing it unlocks the dependent for all their colleagues at once,
not just for whoever pressed Submit.

If you see a warning on the campaign page saying an assessment is answered by a
group that no longer exists, that assessment is hidden from everybody until it
names a list that does exist. The person dialog on the participants tab carries
the matching warning for one person, most often somebody carrying two
department labels, whose department questionnaire is therefore answerable by
nobody.

## Limits and gotchas
- Creating a campaign does not create anything to answer. You still need to add an
  assessment (see
  [Publish and preview an assessment](/operate/tenant-admin/publish-and-preview-an-assessment)).
- There is no separate "campaigns" page. `/<accountId>/dashboard/campaigns` redirects to
  the account dashboard, which is where the campaign cards live.
- Deleting a campaign is not offered in the interface. Set it **Inactive** instead.
- **Contact address for respondents** is per campaign, not per account, and a clone
  carries it over with the rest of the settings. The clone's acknowledgement dialog says
  so and names the address. Change it on the copy if the next round is somebody else's.
- **A carried cohort is not an invited cohort.** The copy's roster is full and its outbox
  is empty; nobody hears anything until you send. That is deliberate: the dates are not
  set yet when the copy is made.
- **"Same person as…" never guesses.** It will not suggest links from matching surnames
  or shared domains, and it refuses outright if the two addresses already belong to two
  different people you linked earlier: joining two groups is a bigger decision and has
  to be made deliberately.

## Related pages
- [Add people to a campaign](/operate/tenant-admin/add-people-to-a-campaign)
- [Publish and preview an assessment](/operate/tenant-admin/publish-and-preview-an-assessment)
- [Review campaign analytics and logs](/operate/tenant-admin/review-campaign-analytics-and-logs)
- [Publish results to a public link](/operate/tenant-admin/publish-results-to-a-public-link)
