Skip to content

Cora suggests the team

Cora, the mission coordinator, can suggest who should be on a mission: people who are already in your organisation, and heroes the mission could call in. She posts the suggestion as a team card in the mission’s chat. All a mission admin has to do is approve it. Nobody is added until they do.

The examples on this page follow an invented bike shop, Kestrel Cycles, and its mission “Autumn launch”.

  • When a mission starts. After Cora drafts the full objectives in a new mission’s first run, she looks at who could help. If someone clearly fits, she suggests a team once. If nobody fits, she says nothing.
  • When you ask. Write “@Cora who should be on this mission?” or “Suggest the team for this”, and she looks and suggests.

A mission has at most one team card waiting at a time. Cora cannot post another until the first is approved, declined or expired (D0871).

Cora reads two lists, and nothing else about anyone:

  • The people of your organisation who are not in the mission yet, with the roles they hold and what each role covers, as org admins set them in People and roles (see roles and approvals). She never sees their email addresses.
  • The heroes this mission could add now: heroes that are on, are open to this mission and are not already added, with what each hero’s card says, its skills and when to call it in.

She matches them to the mission’s objectives and gives each one a reason, such as “Holds the Content lead role: writes the launch copy”, and what they would own in this mission.

Cora only suggests people who are already in the organisation. She never invites anyone: only an org admin invites people to the organisation (see inviting people).

For Kestrel’s “Autumn launch”, the card might read:

Who Why Would own
Mia Chen (Content lead) Writes the shop’s newsletters and product pages The launch copy
Tom Okafor (Workshop manager) Knows the new bikes’ service needs The service checklist
@fleet-desk (hero) Answers stock and warranty questions Stock checks before launch day

Each line has a tick box for a mission admin. Everyone in the mission can read the card; only the mission’s admins can answer it.

One of the mission’s admins answers the card:

  1. Untick anyone you do not want. Everyone starts ticked.
  2. Press Approve. Only the ticked people and heroes are added; the rest are marked “Not chosen”.

Or press Decline, and nobody is added.

An org admin who is not one of the mission’s admins cannot answer the card, just as they cannot add people to that mission by hand (D0872).

What approving does:

  • People join as ordinary members, never as admins. The card has no admin choice: making someone an admin lets them add and remove people and answer the mission’s approvals, so a mission admin does that on purpose in People. Each person is told they were added, and the chat shows the usual line, such as “Megan added Mia Chen and Tom Okafor to the mission and shared all mission history.”
  • Heroes join the mission’s heroes, as Add a hero adds them. You find them in mission details, Tools, under Heroes helping here, and Cora can call them in from then on. The People pop-up stays people only.

Cora’s card can be days old, so Team Cora checks every ticked line again when you press Approve:

  • A person must still be in the organisation and not already in the mission.
  • A hero must still be on, still open to this mission, and not already added.

Anything that no longer fits is skipped, and the card says why, for example “No longer in the organisation” or “Not open to this mission”. The others are still added.

A team card waits 7 days. If no mission admin answers by then, it expires and nobody is added. Team Cora checks every 5 minutes, so it can close up to 5 minutes late. Cora can then suggest a team again.

  • It never adds anyone outside your organisation, and never invites anyone.
  • It never makes anyone an admin.
  • It never opens a hero to a mission its admins left out. A hero closed to this mission is never suggested (see who can call a hero).
  • It never changes a hero’s daily limit or what a hero returns. Each call is checked when it is made, as for any hero (D0873).
  • It never shows what anything costs.

A called hero cannot suggest a team for the mission that called it.

The organisation’s audit history records each suggestion, approval, decline and expiry with who and which people and heroes, never Cora’s reasons. Each person or hero added is also recorded as if a mission admin had added them by hand.