# Add people to a campaign

## Purpose
Put the people being assessed into a campaign, and put reviewers alongside them.

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

## Before you start
- The campaign exists. See [Create a campaign](/operate/tenant-admin/create-a-campaign).
- You know the difference between the two kinds of person here: a **participant** is
  being assessed; an **auditor** reviews someone else's answers. Auditors must already
  be members of the account before you can assign them.

Everything below lives on one screen: open the campaign, then the **Participants &
Roles** tab. That tab has five sub-tabs: **Participants**, **Invitations**, **Campaign
roles**, **Auditor assignments** and **Communications**.

The **Participants** sub-tab opens first: a filter bar with the search box, **Filters**,
**Import participants** and **Add participant**, and the roster underneath it, one row
per person.

![The Participants and Roles tab of a campaign on its Participants sub-tab. Above the roster are the five sub-tabs, a count of 113 participants, a search box, Filters, Add all to CRM and Add participant. Each roster row shows a name and email address, a status with how many assessments have been delivered, the status of each assessment, the email language and the date last active.](/assets/public_doc_images/guides/add-people-participants-tab.webp)

## Add participants

On the **Participants** sub-tab, choose **Add participant** at the right of the filter
bar to add one person, or **Import participants** to add a list. The bar wraps onto a
second row on a narrow window rather than pushing those buttons out of sight.

### One person

The dialog opens on **Existing user** when your account has a member to add, and on
**New user** otherwise.

**Someone already in your account.** The **Existing user** tab lists your account's
members: everyone with an email address who is not already a participant here.
Choose one and select **Add** (it stays unavailable until you have chosen someone). The switch beneath, **Ask them to complete the
registration form first**, decides how they join: off, they can start straight away
and join as **Active**; on, they complete the campaign's registration form first and
join as **Invited**. When the list is empty the tab says why: either the account has
no members yet, or every member is already a participant.

A member with no email address on file is not offered. A participant is identified by
their email address, so there is nothing to add without one.

**Someone new.** Choose the **New user** tab, enter their email address, and optionally
a first and last name, an **Organisation**, a value for each of your label groups, and an
**Email language**. They are created with status **Invited**. The language defaults to
*Not stated*, which is not the same as English: somebody who has stated nothing is
written to in both of your account's languages rather than one guessed at. See
[What language your emails go out in](/operate/tenant-admin/transactional-email-language).

**Email an invitation now** is ticked by default for one person: adding someone and
telling them about it are the same act unless you untick it. The button says which you
are about to do: **Add and email invitation** or **Add without emailing**. Their link
works until the campaign closes; with the box ticked, **Keep the invitation open longer
(days, optional)** only matters if it must last longer than that.

**Organisation** is a typed field with a suggestion list, and the suggestion list is the
point: it offers the spellings this campaign's roster already carries, so the second
person from an employer is recorded under the same name as the first. You can still type
one nobody has used: the first person from a new employer has to be able to. What that
link is for, and how spellings fold together, is under [The organisation on a
participant's row](#the-organisation-on-a-participants-row) below.

**The label selects** appear one per label group your account maintains whose
applicability includes participants; an account with none sees none. Choosing a value
puts that group's chip on the roster row, exactly as the `label.<group>` import column
does. Leaving one on *Not stated* says nothing rather than guessing, and nothing is ever
added to a label group to fit a choice: the options are the labels you already have.

**If this campaign has an assessment answered by an organisation or a group**, adding
someone without one warns you once you have typed their address: a person with no
organisation (or no label, for a group-answered assessment) has nothing to open, and
would land on their "My assessments" page with no explanation. Set the missing fact, or
tick **Add this participant anyway. I understand they will see no open assessments
until this is fixed** to add the row regardless. You can always fix a row afterwards:
see [Editing a participant's details and organisation](#editing-a-participants-details-and-organisation)
below.

### A list of people

**Import participants** (or **Import a list instead**, under the one-person form) opens
its own dialog. Nothing is saved until you confirm, and it works in three steps.

1. **Your list.** Choose a CSV file, or paste the rows. The first row names the columns;
   only an email column is required, and column names are matched without regard to
   case or spacing (`First name`, `firstName` and `first_name` are one column).
   **Download a template (CSV)** gives you a file to fill in, and **Which columns and
   values can I use?** lists them.
2. **Check the rows.** Every row is checked as you choose the file or paste it, and
   shown as **Ready**, **Will update** (already on this roster, by address: their details
   are updated, never duplicated), **Will not be added** (a value the import refuses), or
   **Will be skipped** (an address repeated further down the list; only its first row is
   used), with a sentence saying why: for example *'Organisational respondant' isn't a
   participant class. Use one of: Organisational respondent, Policymaker, …*. Columns the
   import does not recognise are named, so a typo in a header is visible. Fix a refused
   row in your spreadsheet and import the list again: re-importing is safe. The import
   report uses the same words: **Not added** and **Skipped**.
3. **Email them an invitation now?** There is no default: choose **Not now, add them
   without emailing** or **Yes, email each person their invitation now**. The import
   button stays disabled until you have answered. Choosing to email shows two more
   controls: **Also send again to people who already have an invitation** and
   **Keep the invitation open longer (days, optional)**. People added with **Not now**
   read **Not invited yet** on the roster (never *Invited*) and are not counted under
   the Engagement tab's **Invited**. To invite them later, select them on the roster and
   choose **Email links** (this works before the campaign opens, too) or import the
   list again and choose to email them.

Above the button, **When you confirm** says what will happen in numbers: how many people
will be added, how many already on the roster will be updated, how many will be emailed
(or that nobody will be), how many rows will not be added, and how many repeated rows
will be skipped. The button names the count: **Import 6 people**.

**Values in your own words.** Write a participant class, a province, an organisation
size, a discipline or a lifecycle phase the way the app shows it (*Organisational
respondent*, *Ontario*, *Québec*, *1–4 employees*, *Architecture*) or as its short code
(`organisational_respondent`, `ON`, `s1`). Case, accents and punctuation do not matter,
and the French wording is accepted too. What is stored is always the code. *Not stated*
in a cell says nothing, exactly like an empty cell. The `language` column takes `en` or
`fr`, or the language's name (*English*, *Français*).

A province or participant class that names nothing the app knows **skips the row**:
those are closed lists the whole programme reports against, and a person filed wrongly
on one is hard to find again. An organisation size, discipline or lifecycle phase the
app does not offer is kept as typed, with a note saying so.

**Label-group columns.** A column headed `label.<group>` files each person under one of
your own label groups: `label.department` with "Public works" in the cell puts the chip
`department:public_works` on their roster row. The group name is written as one word with
later words capitalised, so a group called "Service area" is headed `label.serviceArea`;
`label:department` and `labels.department` head the same column. Several values in one
cell are separated with `|`. A plain `labels` column is unchanged and still means what it
always did: a free-form list of your own chips, with nothing to exist first.

A `label.*` cell your taxonomy cannot place **never skips the row**: the person is
imported without that chip and the report says which cell was ignored and why: either
the group is not one you have, or that value is not one of its labels. Nothing is added
to your label groups to make a cell fit. A missing chip is fixed by adding the label
under **Labels** and re-importing. The participant class keeps its own `participant
class` column and cannot be set through `label.participantClass`: one row must not be
able to state two classes.

If the campaign has an organisation- or group-answered assessment, the dialog also says
how many rows have neither, and asks you to confirm before they are added.

Someone who already holds a live invitation is *not* sent a second one: a second link
would work independently of the first, so re-importing a corrected list never
double-invites anybody. **Also send again to people who already have an invitation** is
how you ask for them to be chased anyway. It is off by default, and worth understanding
before you tick it:

- The chase is the same **Re-invite** the **Invitations** sub-tab offers, one person at
  a time. It re-uses the existing invitation and mints a **fresh link, so the one
  already in their inbox stops working**.
- It can be held back, per person, and the report says which: an identical message went
  out moments ago (the link they hold still works), the address can't be emailed (see
  [Addresses that can't be emailed](#addresses-that-cant-be-emailed)), or the resend was
  refused (most often because that invitation has already been resent five times this
  hour).
- The list is saved first, so a chase that is refused never costs you the import.

When the import finishes, the dialog shows the **Import report**: one line per row, with
what happened in words (*Added*, *Updated*, *Added · emailed*, *Added · not emailed*,
*Already invited*, *Skipped*, *Not added*) and the sentence that explains anything that
needs one. **Download report (CSV)** keeps the same detail, one line per row.

Participants are not credentialed accounts and no password is set here. Anyone who
needs to sign in does so with their BIMei account.

## Work with the participant list

The filter bar gives you page size, and filters for role, status, label and auditor,
plus a working search box over name, email and id. Switch between **Cards** and
**Table**, and use the **Configure columns** control to choose which columns show and
in what order. One of them is **Language**: what language this person's emails go out
in, or "Not stated".

On a campaign answered **per organisation** (one submission counts for everyone
linked to the same organisation, as in the BIMMaS Pilot), the roster also has an
**Organisation** column, the search box matches organisation names, and **Filters**
offers **Organisation**, where you can tick several organisations at once (and "Not
linked to an organisation"). The Engagement tab lists the same organisations under its
**Completion** band, unfinished ones first, each with a **Follow up** for the people
there who still owe something.

When the window is too narrow for every column, the roster leaves out the least-used
ones (Full Name, Auditor, Language, Last Active, in that order) instead of scrolling
sideways, and says which under the table. **Show all columns** brings them back.

Each row's **⋮** menu offers:

- **View scorecards**: that participant's report page.
- **Download XLSX Report**: a spreadsheet of their submissions.
- **Edit details**: see below.
- **Preview as respondent**: see below.
- **Labels**: the participant class and any free-form labels.
- Status transitions appropriate to where they are (Invited → Active, Active →
  Suspended, and so on).
- **Remove from Campaign**.

A small amber **No organisation** (or **No group label**) badge under a participant's
name means this campaign has an organisation- or group-answered assessment and this
person is not linked to one, so they cannot answer it yet. Hover it for the fix: set
their organisation in **Edit details**, or their group in **Labels**.

## Editing a participant's details and organisation

**Edit details**, on a row's **⋮** menu, opens a small form for that person's first
name, last name and organisation. Labels are edited separately, through the row's
**Labels** action.

**Organisation** is a list, not a text box. It shows the organisations people on this
campaign are already in first, each with how many people it has (the person's own is
marked **(current)**), then the rest of your account's organisations, then **A new
organisation…**. Choose one to move the person there; choose **A new organisation…**
and type its name to create one. If the name you type is already an organisation, the
form says so and they join it; if it only looks like one (the same name apart from
"Inc.", "Ltd." or punctuation), the form points you at the existing one in case that is
what you meant.

Moving a person really moves them, applicants included: their link to the
organisation, the organisation name on their row and the affiliation are changed
together, and the move is recorded in the audit trail with where they came from and
where they went. Saving re-checks their availability for every organisation-unit
assessment in this campaign, so a move can open assessments that were unavailable a
moment ago, or close them.

**What does not move is what they already answered.** If the person has a draft saved,
or has submitted a response, for their current organisation, the form warns you before
you save: those answers stay with the old organisation. It also says how many other
people on this campaign are in the old organisation, so you know whether anyone is left
to carry the draft on. Drafts are never moved for you.

## Seeing what a participant sees

**Preview as respondent**, on a row's **⋮** menu, opens a read-only copy of that
person's own assessments page: the same cards they see, in the language their emails
go out in, with whatever their results page would say about released or withheld
results. It is a picture, not a login: you are not signed in as them, nothing on the
preview submits, opens a questionnaire, creates a participant link or withdraws anyone,
and the buttons are shown disabled to say so. You need the same permission that lets you
edit a participant, and each preview is recorded in the audit log against your name.
Walk-up responses with no email address have no assessments page of their own, so the
action is not offered on those rows.

**Participant link**, on the same menu, lists the assessments that person can open, each
with **Copy link** and **Regenerate**. An assessment they are not offered follows, by its
full name, saying why: **Not offered yet** (a campaign rule decides it, from their answers
to an earlier assessment),
**Not open yet** (it opens once they finish the one it depends on) or **Not offered**,
with no link to copy. The roster's **Assessment Status** column and the person's
completion panel use the same words.

Selecting rows reveals five bulk buttons: **Assign Supervisor**, **Apply label**,
**Send follow-up** (only if you may send communications), **Email links** and **Add to
CRM**. With nothing selected, the last reads **Add all to CRM** (see
[Push people into CRM contacts](/operate/tenant-admin/crm-contacts)).

## Assign an auditor

1. On the **Participants** sub-tab, tick the participants the auditor should cover.
2. Choose **Assign Supervisor (n)**.
3. Search for the member by name or label, choose them, then pick the role to grant
   under **Select Granular Role**.
4. Confirm.

Each assignment is a role granted at *participant* scope, so an auditor sees exactly the
people you selected and nobody else. Review the result on the **Auditor assignments**
sub-tab, where you can also revoke an assignment.

The **Restricted assessment auditor** is not offered here: it is granted on one
assessment, from the **Team** page (see
[Review answers and share feedback](/operate/tenant-admin/auditor-reviews-and-feedback#the-restricted-assessment-auditor)).

The **Campaign roles** sub-tab is the equivalent for whole-campaign grants: someone who
should see the entire campaign rather than named participants.

## Invite people to sign in

The **Invitations** sub-tab lists invitations scoped to this campaign. Its own **Add
people** button opens the same dialog described above. There is one "add a person"
dialog in this product, not one per screen, and every entry point into it writes through
the same request. Use it when participants need to sign in rather than answer an
anonymous public link; the list here updates once the roster write that minted the
invitation lands.

Each row has a **Re-invite** button and a **⋮** menu with **Copy invitation link** and
**Retract invitation…**. **Re-invite** asks first, naming the person (*Send the
invitation to gus@… again?*), because it mints a fresh link and the one already in their
inbox stops working. Afterwards a message above the list says what happened to that
person: sent, not sent because an identical one went a moment ago (with the time it can
go again), not sent because the address can't be emailed, or failed. The list does not
re-sort under your pointer after a Re-invite or a Retract: the row stays where it was
until you sort by a column or reload the page.

### Addresses that can't be emailed

The platform keeps a do-not-email list: usually addresses that bounced or whose owner
reported a message as spam. Nothing reaches an address on it: not an invitation, not a
reminder, not a follow-up. Wherever this campaign shows that person, it says so:

- on the **Invitations** sub-tab their status reads **Can't be emailed (address
  blocked)** instead of *Invitation sent*, and a note above the list says how many people
  are affected;
- on the **Participants** roster their row carries a **Can't be emailed** badge;
- on the **Engagement** tab their **Mailable** column reads **Do not email**;
- in an import report their row reads **Added · not emailed**.

Re-invite on a blocked address offers to **Make a new link** instead of sending one: no
email goes, and the new link replaces the old. The result is said once, as the first line
of the note above the list. Because nothing was emailed, the row's
**Invited on** keeps the time of the last email that did go, and the campaign's audit trail
records a new link rather than a resend. To reach the person, copy their link (the
row's **⋮** menu → **Copy invitation link**, or **Participant link** on the roster) and
send it another way. If the address works again (the mailbox was full, a filter has been
fixed), ask platform support (**Support**, at the foot of every page) to lift the block.
Your account's administrators cannot lift it themselves: the list is shared by every
account on the platform.

### What the invitation carries

The invitation email greets the recipient by name (when you have one on file), names
the account, campaign or assessment they are being asked into, states the role and
the link's expiry, and carries their own signed links to start. It does not carry an
answer to any question in the assessment itself - not a project reference, not a
milestone, not anything else a respondent is asked to type. If a questionnaire asks
for a value "as agreed with your team" or similar (the project-team assessment's
project reference is the current example), the invitation is not where that value
comes from: agree it with the people you are inviting through your own channel
(email thread, kickoff meeting, shared document) before the wave opens, so everyone
answering about the same project types the same string.

## Message the group

The **Communications** sub-tab composes messages to the participants of this campaign,
with the participant list pre-loaded as the recipient set.

For a nudge rather than a message, the campaign header has **Send reminders (n)**, where
*n* is the number of participants who have not finished. The button is hidden entirely
if you lack permission to send; with nobody outstanding it drops the count and reads
**Send reminders**, disabled. Choosing it opens the same follow-up dialog as the
**Send follow-up** bulk button above (there is one dialog, not two), defaulted to
everyone who still owes an assessment.

Reminders and follow-ups cannot be sent before the campaign opens or after it closes.
Until its opening day the header reads **Opens** and the date instead of **Active**, and
**Send reminders** and **Send follow-up** are disabled with the opening date as the
reason; after the close the header reads **Closed** and **Email links** is disabled too.

**Email links** is the exception before the opening: it sends each selected person their
own link, and the email says when the campaign opens and that the link works from then
until it closes. Use it to invite people you imported without emailing: they read
**Not invited yet** on the roster until you do. Invitations (**Add participant** with
**Email an invitation now**, an import that emails, **Re-invite**) also go before the
opening, and say the same.

**A person's first email is never a reminder.** Whichever button you use (**Email
links**, **Send reminders** or **Send follow-up**, before or after the opening),
anybody who reads **Not invited yet** (nobody has emailed them an invitation or their
link) is sent their **personal link**: the subject is *Your link from* your
organisation *for* the campaign, it says nothing about reminding them, and it does not
end with "if you've already completed it". Everybody already written to gets the
reminder. The preview says how many of the audience are getting their link, and the
campaign's audit trail records it as *Emailed their link to* so many people. It does not
count as a reminder anywhere: not in a person's **Reminders**, not in **Last reminded**
and not in the **Last follow-up** figure.

### Choosing who a wave reaches

The follow-up dialog always shows an audience picker before it lets you send anything:

- **Everyone who still owes an assessment** (the default: what the header count means).
- **A segment**: pick the axis (province, sector, organisation size, and so on) and
  then the value.
- **A funnel stage**: not registered yet, registered or started. (Completed people are
  never a target; the campaign is not chasing them.)
- **Pick people**: a searchable, tickable list of named roster rows, for "just these
  two".

Whichever you choose, a **Who this reaches** list appears with the actual names and
addresses (not masked, because you already hold this roster), and it updates the
instant you change the audience. The count that decides whether **Send** is enabled
still comes from the server's own preview a moment later, because it additionally knows
things this list does not (who was reminded too recently, whose address is suppressed).

### Writing the message

The message box adds the recipient's own greeting and their signed links automatically.
Do not type either yourself. If you type a leading line like "Hello," or "Bonjour,"
anyway, it is quietly removed when you leave the field, with a note explaining why. A
**Quick start** picker offers two or three ready-made texts, in English and French, that
you can choose and then edit; a separate **Template** picker (only visible if you may
view communication templates) fills the same two fields from a saved template and
records which one you used.

### People who started without consenting

A response counts only when the person consents **and** submits. Agreeing in a draft
is not recorded as consent, but a reminder does read it, to decide which message to
send. This applies only on a campaign that asks for consent.

- **Started, not submitted, and the draft says they agree**: the ordinary reminder.
- **Started, not submitted, and the draft declined or left the consent question
  unanswered**: the **consent-needed reminder** instead. Its subject is *Your answers
  for* the campaign's name *cannot be counted yet*. It explains that their
  participation can only be counted once they agree to take part and submit, and how to
  do that. It ends with *Don't want to take part? Let us know:* and a **Remove me from**
  link that names the campaign (*Remove me from* and the campaign's name).
- **Everyone else** (people who have not started, people who have submitted anything
  in the campaign, and everyone on a campaign that never asks for consent) gets the
  ordinary reminder, as before.

There is no separate button. The consent-needed reminder goes out with whichever
reminder you send, **Send reminders** or **Send follow-up**, to the people it applies
to.

**It is sent once per person per campaign.** After it, that person gets no further
reminders for the campaign while they still have not agreed. The message tells them
so: it is the only reminder of its kind. If they later save a draft that agrees, they
are back on the ordinary reminder. If they decline again after that, they get nothing:
the consent-needed reminder is never sent twice.

**Who it skips, and how that shows.** The follow-up preview counts the people who
already had their consent-needed reminder among the recipients it skips, alongside
anyone reminded too recently.

**Your words still go in.** If you typed a message, it is added below the
consent-needed wording as a note. Your subject is not used for this message: it was
written for the ordinary reminder.

### The "remove me" link in every reminder

Both reminders carry a **Remove me from** link, followed by the campaign's name (*Remove
me from this assessment* if the campaign has no name to show). On the ordinary one it
follows the question *No longer wish to take part in* the campaign's name. It sits
beside the unsubscribe link in the footer, and it is not the same thing:

- **Unsubscribe** stops every email to that address, from every campaign. The person
  stays in your campaign.
- **Remove me from** (the campaign's name) withdraws the person from this one campaign. The
  link opens a page that asks them to confirm first; following the link alone changes
  nothing, so a mail scanner that opens every link withdraws nobody.

Somebody who confirms is recorded as **withdrawn**, exactly as if they had chosen
**Withdraw from** (the campaign's name) themselves. If they answer as themselves, their answers stop being used in reports from
that day. If they answer for an organisation, the organisation's response stays on file and
in reports. Either way nothing is deleted, they receive an email confirming it, and
reminders and follow-ups skip them from then on. Each link is signed for one person in one campaign and does not
expire.

## The organisation on a participant's row

When you give somebody an organisation (the `organisation` column of an import, the
field on the add form, or the free-text **affiliation**), the platform does not just
store the words. It looks for an organisation of that name in your account, creates one
if it has never seen it, and links the person to it. Everything that reports by
organisation then groups on that row rather than on the spelling somebody typed.

### How spellings fold together

Two people can write the same employer differently and still land on the same
organisation. Before matching, a name is trimmed, its runs of spaces collapsed to one,
its accents removed and its letters lower-cased. So all of these are ONE organisation:

- `Ville de Montreal`
- `Ville de Montréal`
- `VILLE DE MONTREAL`
- `  Ville   de  Montreal  `

The name you see is the FIRST one that was written. A later spelling joins the
organisation; it never rewrites its name.

What does NOT fold: punctuation, legal suffixes and extra words. `Acme` and `Acme Inc.`
are two organisations, and so are `Acme` and `Groupe Acme`. That is deliberate: joining
two firms that are genuinely different is not something this release can undo.

### Fixing a name

If the stored name is the wrong spelling (the first import shouted it, say), rename the
organisation through the API: `PATCH /api/v1/accounts/{accountId}/organisations/{organisationId}`
with `{"name": "Ville de Montréal"}`. You need the same permission that lets you edit a
participant. `GET /api/v1/accounts/{accountId}/organisations` lists them with their ids.

A rename changes only what is displayed. It does not change how names match, so people
who wrote the old spelling stay on the same organisation, and so will anybody who writes
it tomorrow.

### Two spellings of one employer

When one employer has ended up as two organisations ("ABC Consulting Inc." and "ABC
Consulting", say), move the people from one to the other with **Edit details** (see
[Editing a participant's details and organisation](#editing-a-participants-details-and-organisation)).
The emptied organisation stays in your account with nobody in it; nothing is merged
for you. Applications are caught earlier: the **Registrations** page flags an
application that is probably from the same organisation as someone else, and asks you
to choose its organisation before accepting it (see [Run registration
intake](/operate/tenant-admin/registration-intake)).

### What this release cannot do yet

There is no way to SPLIT one organisation into two, or to MERGE two organisations into
one row, from the product: you can only move people between them. If two genuinely
different employers have folded together, raise it rather than trying to fix it by
editing people's rows.

## What happens next
- Participants appear in the campaign counts and, once they submit, in scorecards and
  exports.
- Auditors see their new assignments the next time they open the **Auditor workspace**.

## Limits and gotchas
- Adding one participant emails them an invitation by default (**Email an invitation
  now**; the button reads **Add and email invitation**). Untick it to build the roster
  first and invite people later. An import never emails anyone unless you choose to.
- Removing a participant from the campaign does not delete submissions they already
  made.

## Related pages
- [Publish and preview an assessment](/operate/tenant-admin/publish-and-preview-an-assessment)
- [Review answers and share feedback](/operate/tenant-admin/auditor-reviews-and-feedback)
- [Push people into CRM contacts](/operate/tenant-admin/crm-contacts)
