# Run registration intake

## Purpose
Publish an application form, review who applies, decide, and get the answers out as a
file.

## Who this is for
Account administrators and whoever handles applications.

## Where this lives

**Registrations** in the sidebar. The page is titled **Registrations** too, and its
real URL is `/<accountId>/dashboard/team/triage`, one level under Team & Access, which
is why its breadcrumb reads **Team & access › Registrations**.

The page leads with the **Applications** to decide. With more than one form, each
application names the form it came through, as a link to that form. Below them,
**Registration forms** lists your forms: how each one works (who can open it, whether it
has an entry code, whether applications are accepted as they arrive), how many of its
applications are left to decide, and **Open**.

Everything you set up once lives on the form's own page,
`/<accountId>/dashboard/team/triage/forms/<formId>`, titled with the form's name. Its
breadcrumb reads **Team & access › Registrations › *form name***, and beside the title
are **Switch form** (to another of your forms, on the same tab), **See its
applications** (the list above, showing only this form's) and **Open the form** (the
public page applicants use). The settings are in four tabs:

- **Form**: the name, the template whose questions applicants answer, the public key,
  and **Accept applications automatically**;
- **Sharing**: who can open the form, the websites that may show it, and the optional
  entry code;
- **Actions**: what happens to an applicant, under the decision that runs it;
- **Triage assistant**: whether the assistant may review applications, and its rules.

**Form**, **Sharing** and **Triage assistant** edit one record: **Save form** on any of
them saves what you changed on all three, and **Unsaved changes** shows beside the tabs
until you do. The entry code and each action save on their own.

The sidebar entry only appears if your role carries registration permissions.

## Create a form

Under **Registration forms**, choose **New form**:

1. On **New registration form**, fill in the **Form name** (required) and the
   **Template id** (required): the assessment template whose questions applicants
   answer. Copy the id from the ID line under the template's name in the
   **Assessments** library; the field names the template as soon as it is found. (There is no list to pick from: the template list carries every
   template's questions, which is too much to load for a name.) An existing form shows
   its template by name, as **Questions from**. Choose **Change** to give it another
   id.
2. Optionally set a **Public key** and a **Description**, then choose **Create form**.
   The new form opens on its own page.
3. On **Sharing**, set who can reach it:
   - **Anyone with the link can open the form**: the form is reachable at all.
   - **People can apply without signing in**: off means applicants must sign in first.
   - **Can be shown inside other websites**: off means the form refuses to run inside
     another site's page and offers a button to open it directly.
4. On **Form**, **Accept applications automatically** is off by default. On, each new
   application is accepted the moment it is submitted, and the applicant gets one email
   to confirm their address and start. See [Accept applications
   automatically](#accept-applications-automatically).
5. On **Triage assistant**, **The triage assistant may review applications** says
   whether the assistant may suggest a decision. In **Rules for the triage assistant**,
   put one rule per line. These are the plain-language rules the assistant is asked to
   apply, and they are shown back to you under **The rules as saved**. A form with no
   rules does not offer the assistant at all.
6. Choose **Save form**.

The form's own id and its template's id are under **Technical details**, for a support
request.

Applicants then use `/register/<formId>`, usually through **Participate** on the
campaign's public page. Everything a participant reads on this path says *participate*
and *responses*: the words *registration* and *application* are the console's, and a
participant never sees them. The form runs in the same page layout respondents later meet in
the questionnaire: your account's logo and the campaign's name at the top, with the
language switcher (**EN** / **FR**) and **More** (holding **Help**) beside them, in the
same place as on the campaign page, the welcome page and the questionnaire; the heading
**Participate in *campaign name***
under your account's name and one short introduction (your template's description, or
the form's when the template has none); the questions as cards; and one **Submit
responses** button under them. The browser tab reads "Participate in *campaign name*". The language the visitor chose on the campaign page carries through, and
changing it in the header switches the form in place without losing what was typed.

**The address is the form's first question.** If your template asks for the applicant's
own address (a single-line email question named, for example, `email` or `workEmail`),
that question is moved to the top and becomes required; otherwise the form adds an
**Email address** question at the top. The application is filed against it, and the
decision is sent to it. A template that asks someone else's address (a
`supervisorEmail`, say) keeps that question where it is.

**One application per address.** If an application from the same address is still
waiting for a decision on this form, submitting again files nothing: the participant
reads **You have already responded**, "We already have responses from *address* for
*campaign*. We're reviewing them and will email you, so there is nothing more to do. If
something has changed, use Contact us." **Contact us** writes to the campaign's own
contact address when it has one, and opens the support page otherwise. Nothing about the
earlier application (its date or anything in it) is shown.

On a form that accepts applications automatically, the same is true of an address you
have already let in: one with an accepted application on this form, or already on the
roster of the form's campaign (an invited participant who applies anyway). Nothing is
filed, and nobody is accepted again or moved into another organisation or unit, whatever
code they enter. Their personal link is emailed to them again, and the screen says "We
already have responses from *address* for *campaign*. We have emailed your link to that
address again." The link goes out at most once every ten minutes per person, and only
that sentence is shown when it actually went; otherwise the screen says there is nothing
more to do.

On a form where you decide each application, that rule does not apply. An invited
participant already on the roster can fill in the form too, and an address you accepted
can apply again: each new application is filed and waits for you under **To decide**.
Accepting an invited participant's application updates the roster row they already have;
it does not add a second one.

An address whose application you **declined** can apply again. The new application is
filed and waits for you under **To decide**, even on a form that accepts applications
automatically: the switch never overturns your decision.

Every form ends the same way, whatever questions your template asks: a required tick,
**I agree to the privacy statement and terms**, as the last card above **Submit
application**. It is the form's only agreement: a template question named `acceptTerms`
(the Pilot kit's earlier "Terms" tick) is not shown, so nobody ticks twice. The words
*privacy statement* and *terms* open the **Terms and privacy** drawer at your account's
privacy statement and terms of use; **Terms and privacy** under the button opens the
same drawer, which also holds Assessor.io's Privacy Policy and Terms of Use. None of
these leaves the form. Submitting without the tick lists "Tick the box to agree to the
privacy statement and terms before you submit your responses." in the summary at the
top of the form, with a link to the tick, and nothing is filed. You do not need a
consent question of your own for this agreement. An application records the versions of
both sets of terms it was agreed against. Applications filed before the tick existed
carry those versions although nobody was asked.

After submitting, the participant sees "Thank you, your responses are in", "We'll
review your responses and email you at *address*. You do not need to do anything else.",
and a short reference. On a form that accepts
applications automatically they see **Check your email** instead: "We've sent a link to
*address*. Open it to confirm your address and start."

If the form is attached to a public campaign *and* that campaign has registration
enabled in its access settings, the campaign's public page shows a **Participate**
button pointing at it. Attaching the form alone is not enough.

## Set up what happens after a decision

**Registration actions** (the form's **Actions** tab) turn a decision into work. An action has a
title, **When it runs** (**When accepted**, **When waitlisted or held for review**, **When
declined**, or **On submission** for a track), **What it does**, and what it applies to:

- **Add them to campaigns**: put the applicant on the chosen campaigns' rosters.
- **Tag them on campaigns**: the same, carrying the action's tags.
- **Give team members a role over them**: the chosen team members get the chosen role
  over the applicant.
- **Tag team members**: add the action's tags to the chosen team members.
- **Email team members**: send the chosen team members the action's message.

Choose **Campaigns** and **Team members** by ticking them in their lists, and the **Role
they get** from its list. A campaign or person the account no longer has stays ticked,
named as such, until you untick it: opening an action never quietly drops one.

**When it runs** is the only setting that decides it: saving the action puts it on that
decision's list, and changing it moves the action. Waitlisted and held for review are
one choice because each runs on both.

The list is headed with the form's name (**Actions for "…"**), and the editor beside it
says which form a save lands on, so the form you are configuring is named wherever you
are on the screen. Each action sits under the decision that runs it (**When accepted**,
**When waitlisted or held for review**, **When declined**, and **On submission** when the
form files on a track), and reads as one line, for example "Add them to campaigns:
BIMMaS Pilot · On". Within a decision, actions run from top to bottom; the arrows on a
row move it earlier or later, and the new order is saved straight away. Its stored codes
and ids are under **Technical details**. The bin icon asks before it deletes an action; what the action
already did for earlier applications stays done.

A save that is refused says so, with the reason, and leaves the editor as it was so you
can correct it and save again. An action needs a title before it can be saved.

**Tags** is the exception: it takes free-form text, not ids. Whatever you type there is
merged onto the person's labels on their campaign roster row or membership, so it is how
you mark a cohort you want to filter on later: `wave:a`, `vip`,
`source:registration_form`. Nothing has to exist first, and these are not label ids: the
field was called "Label IDs" until it was renamed to stop that reading. Actions saved
before the rename keep working, and are read back under the new name.

### Capture the organisation and a group label from the answers

An **Add User To Campaign** action carries what the applicant told you onto their roster
row, instead of leaving it in the submission for somebody to type in again afterwards.

**Their name and job title need no setting.** A question named `firstName`, `lastName` or
`jobTitle` (or any spelling the participant import accepts as a column heading, such as
`first_name`, `surname` or `role`) fills the roster row's first name, last name and role
when the applicant is accepted. If the person was already on the roster (you imported
them before they applied), only the parts their row left blank are filled: your own
spelling of a name always stands.

Two more fields carry the organisation and your own labels.

The two fields sit together in a box headed **What this form captures about the
applicant**, with a **Preview** underneath that reads back what a save will actually
capture: one line per field, naming the question each one reads.

**Organisation** is the form question whose answer is the applicant's organisation.
Choose it from the form's own questions: open the field, then search by the words
applicants see or by the question's name, and pick one (the arrow keys and Enter work
too). Each question shows its page, its name, its kind and, when it has fixed answers,
those answers; one worded like an organisation is marked **Suggested**. **None** leaves
the field empty. What is saved is the question's name. When the applicant is accepted, the organisation named by that answer is matched against the
organisations your account already has, one is created if it is new, and the person is
linked to it. That link is what lets a report group by employer rather than by the
spelling somebody typed; the matching rules are the same ones the import uses, described
under [The organisation on a participant's
row](/operate/tenant-admin/add-people-to-a-campaign). An applicant who leaves the question
blank is linked to no organisation, never to an empty one.

A question the form no longer has (its template was edited after the action was saved)
stays in the field, marked **Not on this form**, until you choose another: opening the
action never drops it quietly. If the form's template cannot be read, the field is a
typed box instead and says so: type the question's *name* from the template, not the
words shown on the form.

**Add a label field** does the same for your own label groups. Each row is a pair:
choose the **Label group** from the list (it offers the groups from **Labels** in your
account settings whose applicability includes participants) and choose the **From
question** whose answer files the applicant under it, from the form's questions as for
**Organisation**. A question worded like the group is marked **Suggested**, and a
question's fixed answers are listed beside it, so you can check them against the group's
labels before you save. Add as many rows as the form feeds,
and **Remove** the ones you no longer want. When the applicant is accepted, their answer
becomes a label of that group on their roster row.

Two rows naming the same group is a half-finished edit rather than a choice: the last one
wins, and the preview shows you which.

If the list of groups is empty (the account has none that apply to participants, or the
read failed), the row falls back to a typed box, and what you type there is the group's
*key*: one word with later words capitalised, so a group called "Department" is
`department` and one called "Service area" is `serviceArea`.

Three things are worth knowing before you rely on it:

- **The group has to exist.** Naming a group your account does not have is refused when
  you save the action, and the message lists the group keys you can use. It is refused
  then rather than ignored later, so you never leave a rule configured that could not
  fire.
- **An answer that matches no label of the group is reported, not refused.** The
  applicant is still accepted and every answer that did match is still written; the
  decision's result names the answer that could not be placed. The fix is either to add
  that label to the group or to correct the form's choices: the message is there so you
  can tell which.
- **Nothing is ever created in your taxonomy to make an answer fit.** A label group is a
  controlled list you maintain, and an intake door that could add to it would fill it
  with misspellings.

If the form asks a question in words that do not match your label names ("Public Works
Department" where the label is "Public works"), an action can carry a translation table
between the two. There is no field for it on this screen yet; it is set through the API
(`valueMap` on a label mapping) and this screen carries it through untouched when you
edit the action.

An action set to run on a decision that does not run it is listed under **Not running**,
with the reason. It can happen to an action saved before a decision's list and the
action's own **When it runs** were one setting. **Run it when …** on the row puts it on
its decision's list; until then it runs for nobody.

### File each submission on a track

A form can file what people send on one of the account's tracks as it arrives, instead
of waiting for a decision: an expression of interest from an organisation, for example.
Create an action with **When it runs** set to **On submission** and **What it does** set to
**Add to a track** (each sets the other: no other action runs on submission, and this one
runs on nothing else). Then fill in **Filing on a track**:

- **Track**: the track the submissions go on.
- **Stage a known organisation moves forward to**: for an organisation already on the
  track, the stage it moves to (for example **EOI received**). It only moves forward
  from an earlier progress stage, never back and never out of an exit stage such as
  **Not now**. Leave it at **Do not move it** to leave the stage alone.
- **The questions that carry the request**: the form's questions for the sets ticked,
  the role asked (lead, co or unsure), a new topic, the website, the job title and the
  preferred language, each chosen from the form's questions as for **Organisation**.
  Leave any your form does not ask at **None**.
- **Consent question** and **Answers that decline consent**: an answer listed here
  means nothing is kept: no application, no contact and nothing on the track. The
  applicant is told their responses were not kept because they did not agree, and can
  fill in the form again.
- **Organisation**, under **What this form captures about the applicant**, is required:
  the question whose answer names the organisation. The label fields there name the
  organisation's label groups (type, province, reach).

Each name must be a question of the form; the save says which ones are not. When a
submission arrives:

- a new organisation goes on the track at its first stage, with Source
  **Self-referred**; the platform says in the entry's history (and in its next action)
  when it is probably the same as an organisation the account already has, and never
  merges them;
- the entry gets the request (sets, role asked, new topic) and the next action
  **Review the expression of interest**, due that day, unless it already has one;
- the organisation's empty profile fields are filled from the answers; anything it
  already has is kept, and the dialog offers **Update to newest** where the newest
  answer differs;
- the person who sent it is linked to the organisation, as its primary contact when it
  has none;
- the application is marked **Filed to track**. It is reviewed on the track, never
  accepted here, and the same person can send another later, which replaces the request.

An answer that matches no label, or a mapped question the form no longer has, is noted
on the application, under **Filed to track**, and the rest is filed. If filing fails,
the application waits under **To decide** as on any other form.

## Give some applicants an entry code

An **entry code** is an optional code on the application form, for a group you invite
in a different way from everyone else: for example the units of one department, who
should answer an extra Specialised Set and each answer as their own unit rather than as
the whole department. You give them the code (by email); an applicant who enters it is
placed in their unit and given the labels you chose, and nobody else is.

Set it on the form's **Sharing** tab, under **Entry code**:

- **Code**: type one, or choose **Generate** for a 12-character code shown in groups of
  four. A code needs at least 10 characters, not counting spaces, 6 or more different
  ones, and not one or two common words. Applicants may type it in capitals or not, with
  or without the spaces. **Copy it before you save**: it is stored so that nobody can
  read it back, on this screen or anywhere else. To change it, type or generate a new
  one; the old one stops working. Leave the field empty to keep the current code while
  you change anything else.
- **Labels a valid code adds**: participant labels, separated by commas, for example
  `institution:acme`. A campaign rule that opens an assessment only to people with that
  label then opens it to code holders.
- **Label group that lists the units**: one of your account's participant label groups,
  for example "Unit within organisation". Its labels are the units an applicant chooses
  from.
- **Organisation prefix**: for example `ACME`, so a unit is recorded as the organisation
  "ACME: Technical Centre".
- **Unit question, in English** and **in French**: the title of the question that
  replaces the organisation question, for example "Your ACME unit".

**Remove code** turns it off; applications already received keep their unit and labels.

**On the form**, a **Code** question appears just before the organisation question,
with the hint "If you were given a code, enter it here." (in French when the applicant
reads French). When the applicant enters a code, the page checks it. A valid code
replaces the organisation question with the unit question: a list of the units plus
**Other**, which asks them to type their unit. A wrong code is marked on the field and
the organisation question stays. The code is checked again when the application is
submitted, and a wrong one is refused there too.

**What is recorded.** The code itself is never stored with the application, its
answers, exports or emails. The application's organisation answer is filed as
`<prefix>: <unit>`, and the application records that a valid code was entered, with the
unit and labels it applies. Its **Details** say so.

**At acceptance**, the labels and the unit's label are added to the participant, and a
unit typed under **Other** is added to the label group, so later applicants and your
reports see it. A code holder joins their unit's organisation when it already exists,
so colleagues from one unit answer together, and a new unit becomes a new organisation.
The same-organisation flag (below) is never raised for a code holder, so **Accept**
does not ask which organisation for them. On a form that accepts applications
automatically, a code holder is always accepted automatically, into their unit (see
[Accept applications automatically](#accept-applications-automatically)).

## Review an application

**Applications** lists one row per applicant: their name, email, organisation and job
title (as their answers gave them), the date they applied, the short reference they were
shown when they applied (quote it back to find their application), and a status: **Pending**,
**Needs review**, **Waitlisted**, **Accepted** or **Declined**. Above the list, choose
which to show: **To decide** (Pending and Needs review; the page opens here whenever
anything is waiting), **Waitlisted**, **Accepted**, **Declined** or **All**. An account
with more than one registration form also gets a **Form** filter.

Decide from the row with **Accept**, **Waitlist** or **Decline**. Recording a decision does
two things: it sets the status, and it runs the actions bound to that outcome. The row
then reads, for example, "Accepted by Robin Reviewer on Oct 10, 2026, 1:14 p.m.", and
stays where it is until you change the view, so the next application never slides under
your pointer.

To accept several at once, tick them (or tick the box above the list to select every
application shown that is not yet accepted) and choose **Accept selected**. You are asked
once; each applicant is then accepted in turn, and anyone who could not be is named and
left ticked so you can try again. An application flagged as possibly the same
organisation as someone else (below) is never accepted this way: it is left ticked, and
the confirmation and the result say how many need a decision about their organisation.

### Two applicants from the same organisation

A campaign answered per organisation (the BIMMaS Pilot) takes one response from each
organisation, and the people in it share that response as colleagues. When two people
from one employer apply, it is your decision where the second one belongs, and the page
helps you make it.

**The flag.** An application that is probably from the same organisation as somebody
else carries a quiet line under its details, for example "Possibly the same
organisation as ABC Consulting: Jane Doe (accepted), J. Smith (pending)". Choose it to
see who, with each person's email, organisation and why they matched, and **Open their
application** to jump to another applicant's details. An application is flagged when,
compared with the other applications on the same form (pending, under review,
waitlisted or accepted) and with the people already on the campaign's roster, one of
these holds:

- **The same name, once legal suffixes and punctuation are set aside.** Accents, case
  and spacing are ignored as everywhere else, and so are "Inc.", "Incorporated", "Ltd.",
  "Limited", "Ltée", "Limitée", "Corp.", "Corporation", "LLC", "LLP", "LP", "PLC",
  "ULC", "Co.", "Company", "Cie", "S.E.N.C.R.L." and similar at the end of the name, a
  leading "The", and "&" against "and". The names must then be equal: there is no
  "close enough" matching, because a wrong flag is worse than none.
- **The same work email domain**, compared in full, subdomains included. Public mail
  providers (gmail.com, outlook.com, hotmail.com, yahoo.ca and the like) never count,
  nor do government-wide addresses that many departments share (canada.ca, the bare
  gc.ca, and the provinces' shared hosts). A department's own address, such as
  tpsgc-pwgsc.gc.ca, does count.
- **Someone on the roster already linked to an organisation of that name.**

Nothing is ever merged or linked by the flag itself, and applicants are never shown
anything about other organisations.

**The choice at Accept.** Accepting a flagged application asks **Which organisation?**,
naming the applicant, with one option per existing organisation they could join, each with how many
people are in it already ("Join ABC Consulting Inc. (2 people already)"), and **Create a
new organisation: …** with the name they typed. Nothing is chosen for you, and
**Accept** stays unavailable until you choose. Joining links them to that organisation,
so they share its response; creating keeps them on their own. (When the name they typed
already is one of your organisations, only joining it is offered, because that is what
accepting would do.) **Cancel** accepts nothing. Your choice is recorded with the
acceptance, and re-running the Accepted actions later places them the same way.

If someone is placed in the wrong organisation anyway, move them from the participant
list with **Edit details** (see [Add people to a
campaign](/operate/tenant-admin/add-people-to-a-campaign#editing-a-participants-details-and-organisation)).

**Details** on a row opens:

- **Answers**: each answer under the question the form asked.
- **Decision**: who recorded the current outcome and when, and the triage assistant's
  suggestion if it was asked. An accepted applicant is moved to **Waitlist** or
  **Decline** from here, after a confirmation that says what that withdraws.
- **Reviewer notes**: an internal thread, signed with each author's name; type a note
  and choose **Save note**.
- **More actions**: **Ask the triage assistant** and **Release decision**, when they
  apply.
- **Technical details**: the application's reference and its answers exactly as stored,
  for correcting a mis-keyed answer or quoting in a support request.

### What an acceptance sends

Accepting does more than set a status. In one transaction it emails the applicant an
acceptance letter, mints an invitation for them, and emails that too, and the second
message matters more than it looks. An invitation's activation link is the only readable
copy of its token: the token never appears in the submissions list, in an export, or in
any API response, so an invitation that is minted and not mailed is an invitation nobody
can use.

Both messages can be refused, and the screen tells you which:

- **The address is on the suppression list.** Nothing goes to it: not the letter, not
  the invitation. The applicant is still accepted; they simply have no way in until you
  pass the link on yourself, or an administrator removes the listing. An address lands
  there after a hard bounce, a spam complaint, an unsubscribe, or a manual entry.
- **An identical message went a moment ago.** Somebody applying twice is accepted twice,
  and the second acceptance finds their invitation still live rather than minting a new
  one. Re-sending it would put two messages carrying one link in their inbox, so the
  second is refused and named instead. Nothing is missing: they are holding it.

Silence means both messages went.

The letter names what the applicant was accepted into by its own name ("Your
request to participate in "BIMMaS Pilot" has been accepted"), greets them by the first name their
form gave, and says plainly that their invitation, with their personal link to start,
follows in a separate email. (When the accept actions add the applicant to no single
campaign, the letter names the registration form instead.)

### Accept applications automatically

With **Accept applications automatically** on (on the form's **Form** tab), nobody
needs to press **Accept**. A new application is accepted the moment it
is submitted, by exactly the same acceptance a person's **Accept** runs: the form's
Accepted actions put the applicant on the campaign's roster, an invitation is minted,
and the decision is recorded. Three things differ:

- **One email, not two.** There is no acceptance letter. The applicant gets one
  message, from your account's name: "You've applied to join *campaign*. Confirm your
  email to start.", with their own link as the **Confirm and start** button (in the
  language they read the form in, when they chose one). Following that link is the
  confirmation: it opens the campaign's welcome page, then the questionnaire.
- **The applicant's screen says "Check your email"**, with the address the link went
  to, and nothing about a review or an outcome.
- **The record says it was automatic.** The application's **Decision** reads "Accepted
  automatically on *date*", and the account's and the campaign's activity logs show the
  acceptance by **Automatic registration triage**, not by a person.

**Some applications still wait for you.** An application flagged as possibly the same
organisation as somebody else (see [Two applicants from the same
organisation](#two-applicants-from-the-same-organisation)) is never accepted
automatically, because colleagues of one organisation see each other's answers and
nobody is put into an organisation on a guess. It waits under **To decide** exactly as
it would with the switch off, and the participant sees the ordinary "Thank you, your
responses are in" screen. So does an application from an address you declined before. The same happens if the automatic acceptance cannot be
completed for any reason: the application is always kept, and waits for you. An
applicant who entered a valid [entry code](#give-some-applicants-an-entry-code) is never
held this way: the code places them in their unit.

While the switch is on, a campaign whose access is **By invitation** says **Open
participation** on its public page and on its card in the front page's list, because
anybody who applies is let straight in. A campaign's own access setting is not changed.

The switch is off on every new form and on a form copied with its account, so turning
it on is always a deliberate choice. Accepting manually, from the queue, works as it
always has, with both emails.

**Ask the triage assistant** (under **More actions** in Details) gives the application's
answers and the form's prompt rules to the assistant, which suggests **Accepted**,
**Declined** or **Needs review**. The suggestion is applied (it sets a status and runs the
bound actions like a human decision would), and it is recorded in **your** name: the
row reads "Accepted by" followed by your name, and the assistant's reasoning appears under **Triage
assistant's suggestion**. Treat it as a recommendation you are accountable for, not an
unattended process.

The assistant never accepts an application flagged as possibly the same organisation as
someone else: choosing its organisation is yours to do. When it would have accepted one,
the application is set to **Needs review** instead, and its reasoning starts by saying
why it was held.

## Edit an applicant's answers

Open **Details**, then **Technical details**, and choose **Edit answers**. The answers become an editable JSON document.
It must stay a valid JSON object: anything else is refused with "Answers must be valid
JSON." or "Answers must be a JSON object." **Save answers** records the change against
your user in the audit trail; **Cancel** discards it.

This is a raw editor. There is no form view of someone else's application on the admin
side.

Applicants can also edit their own answers, but only if they applied **while signed in**,
and only before a decision is recorded. Their page is `/registrations/<submissionId>`.
Applications submitted anonymously carry no user identity, so those applicants have no
self-service page at all; changes for them have to go through you.

## Export the answers

**Export applications** in the page header, with an **Export as** selector (**CSV**,
**JSON**, **Excel (XLSX)**) beside it. It exports every application in the account or,
when the **Form** filter above the list is set, only that form's.

The file downloads directly and includes the per-question answer matrix, not just
metadata. Export is permission-gated on the server; if you are refused, the reason is
shown.

## Re-run a decision's actions

A decision's bound actions run once, as the decision is recorded. **Release decision**
(under **More actions** in an application's **Details**) clears that record, so the next
time the application is given the same decision the whole set runs again: the way out
when the actions ran with the wrong configuration, or a message went to a mis-keyed
address.

Releasing sends nothing by itself. The note under the decision says which decision's
actions are re-armed and when they last ran, in your own time zone. Beneath it, a button
named for the decision (**Run the Declined actions again**, say) runs them now: you are
shown the actions that will run, by name, and asked first. (It is offered to whoever may both change an application's status
and edit registration forms; otherwise the actions run the next time the application is
given that decision.) Pressing it twice runs nothing twice: the second press reports that
the actions already ran. What the re-run sends is worth understanding before it happens:

- Every action runs again. Three of the four are idempotent (they add somebody to a
  campaign, assign a reviewer, apply labels), so re-running them changes nothing.
- **Email team members** is the one that reaches a person. It goes out again *unless
  an identical message already reached that member in the last hour*, in which case it
  is refused as a duplicate and reported back to you rather than delivered twice.
- So if the point of the re-run is to send a corrected message, **edit the message
  first**. An unchanged message inside the hour will not go.

Two different applicants tripping the same action still each get their own notice; the
refusal only applies to the same message, to the same person, twice.

## Limits and gotchas
- Accepting an application always emails the applicant twice: the acceptance letter and
  their invitation link. Anything beyond that (a note to your team, a place on a wave)
  is what the actions bound to the Accepted branch do.
- Declining, waitlisting or sending an application back for review emails the applicant
  nothing by itself. Only the Accepted branch has mail of its own.
- The applications list is filtered by status but not paged. On a busy form, **All** is a
  long list.
- Deleting an action also removes it from any branch it was bound to.
- An **On submission** action is bound to no decision, and is listed under **Runs on
  submission**. It runs on every submission while it is on.
- A submission whose consent answer declines is not kept at all, so it never appears
  under **Registrations**.
- The same-organisation flag compares applications on the same form and the roster of
  the campaigns that form's acceptance adds people to. Two applicants on different forms
  are not compared.
- An applicant who entered a valid entry code is never flagged as possibly the same
  organisation as someone else: the code places them. Applicants without a code can
  still be flagged against them.
- Running the Accepted actions with **Run the Accepted actions again**, or through the
  API, for a flagged application nobody has accepted yet is refused: accept it first,
  choosing its organisation.

## Related pages
- [Create a campaign](/operate/tenant-admin/create-a-campaign)
- [Add people to a campaign](/operate/tenant-admin/add-people-to-a-campaign)
- [Push people into CRM contacts](/operate/tenant-admin/crm-contacts)
