ITU · Cybersecurity Capacity Development Tabletop

TTX Captain — User Guide

You are the captain. You click. The table talks. People watching only watch.

Who sits where

After the exercise starts, the captain can open Share view so observers join without a password. See Share the view.

Before you start

You need:

1. The exercise URL from your organiser.
2. Your username and password (passwords are created by admin and handed out — you cannot set your own).

Usernames are the country or short name, lowercase — for example valmera or csa. Password is {username}-### — for example valmera-482, csa-101, or north-111. Login does not care about capital letters. Valmera and valmera both work.

Sign in

1. Open the exercise URL.
2. Type your username (country or short name, lowercase).
3. Type your password. It is {username}-###.
4. Press Enter, or tap Sign in →.

If you see “This account has no password yet”, admin has not generated passwords — wait for the organiser.

On success you land as captain of your team. Until Round 1 starts you see the lobby.

Your captain password stays until the organiser generates a new one or resets your row. Ending, restarting, or changing the scenario signs you out; use the same password unless the organiser tells you it changed.

Wait in the lobby

You will see Welcome, captain of [your team] and Waiting for admin…

Do nothing. Stay signed in. When staff start Round 1, Play opens on its own.

If the session is later terminated, you see a closed-table message. Wait for facilitator instructions (restart or end of day).

Open Play

After the exercise starts, use the primary navigation in this order: Play · Cards · Briefing · Standings · Messages. Open More → Feedback when the facilitator asks you to complete the evaluation.

Header

• Round / phase steps and the live timer.
• Your username chip and Log out.
• Optional colour theme switcher · Help opens this guide in the same tab. Back to exercise returns without signing you out.

Round focus

At the top of Play, read this round’s title and short This round brief. Concrete mission objectives and card deliverables live under Mission progress.

Top stats

• Team name and mission text.
• Budget — money available this exercise.
• Your team (people) — people do not refill each round; assign carefully.

Neighbour status pills

Other teams show Deciding or Turn ended. You can see who has submitted. Captains cannot open another team’s table (staff can).

Choose cards

Six capability tracks (lanes). Scroll the lane strip sideways on small screens.

Filters use those four words: Built / Ready / In plan / Locked. There is no “Open now”. When you pick one domain (one track), cards show as a grid.

1. Tap a Ready card.
2. Tap Add to plan (or remove it if you change your mind).
3. Find it under Your plan this turn.
4. Write a short rationale (why — kept for the debrief).
5. Tap Submit when the table agrees.

After you submit, wait for the facilitator to advance the round. Do not refresh frantically — state syncs on its own.

Specials (Talk & trade panel)

Specials spend budget/people immediately when allowed; the session must be running and not paused.

When a message pops up

When an inject hits your team, a card opens over the game. It may be a warning or an assistance opportunity. Read What happened, then review Impact on your team: the outcome, budget, people and preparedness are specific to your team. Early rounds may show a round guardrail when the applied impact is milder than the authored crisis. If the scenario permits it, the card also shows which capability checks passed or were missing.

1. Read What happened.
2. Read Impact on your team (money, people, preparedness).
3. Early rounds may show a round guardrail — a milder hit than the full crisis.
4. Tap Acknowledge inject when the table has heard it.

You can acknowledge at most two notices in a queue. Effects are already applied. Acknowledge does not apply them again. The card cannot close with Escape or a click outside.

Поделиться просмотром

1. В Play нажмите Поделиться просмотром.
2. Продиктуйте 6-символьный код стола или скопируйте URL.
3. Наблюдатели открывают /app без пароля капитана, выбирают Есть код стола? и нажимают Войти. Или открывают ссылку /app?view=….

What happened so far

Your team log lists builds, trade messages, aid, and inject outcomes for the session.

Look at Standings

Standings is your personal scoreboard:

• Budget and people.
• Counts per track: Built / Ready / In plan / Locked.
• Full card list with filters — open a card, or add a ready card to this turn’s plan.

Use it to plan the next investments without hunting through all lanes.

Open Briefing

Briefing is a hub with two sub-tabs:

The scenario image is one visual chosen by staff — not three separate uploads. The badge tells you what it shows; staff may also set an optional custom image name beside the badge (required when the type is Other):

When markers are available, select a marker—or its matching team row—to inspect that country, agency, or organisation. The detail panel shows its mission, maturity, threat context, and whether an inject is live, queued, resolved, or absent. Your own marker is identified as Your team.

Your Team briefing may also include a structured Mandate and operating position: decision authorities, assets, dependencies, vulnerabilities, red lines, and negotiation goals. Use it to decide what you can commit and what you need from other teams. Other captains cannot open your private Team briefing.

Objectives live on the Team page. Captains are read-only on both. Facilitators with Library rights (or admin) can change the image and its type; captains cannot.

Browse Cards

The catalogue explains each capability before you invest. Open a card and read:

• Read-only for captains (no create/edit unless you somehow have staff rights — you will not in a normal workshop).
• Prerequisite / unlock details may be shown or hidden depending on staff settings — if you don’t see them, use Play lanes and Standings instead.

Send messages

Messages supports negotiation and coordination. You can message other captains at any time; facilitators and admin are available only while shown online. Use the room conversation for urgent decisions and Messages for a recorded follow-up.

Feedback is the participant assessment. Complete it when the facilitator requests it. Your answers help staff assess learning and improve the exercise.

Trade (P30)

Under Talk & trade → Trade with a neighbour:

Trading unlocks only when both teams have built card P30 (Establish CS capacity building for diplomats). Until then you see a locked message.

When unlocked:

1. Agree the deal at the table (face to face).
2. Choose partner team, buy or sell, money or people, amounts, and price ($ thousands).
3. Send the offer.
4. Receiving captain Accepts or Declines in their inbox.

Facilitators can also move people through Run → Master Dashboard → Specialist transfer — that is separate from captain offers.

Ask a neighbour

Different from P30 trading:

You do not move resources yourselves for aid. Watch your log for “waiting for facilitator” and grant messages.

Use a phone

Play is usable on phones and tablets:

• Swipe lanes sideways — track columns snap as you scroll.
• Your plan this turn sticks near the top on narrow screens so submit stays reachable while you browse cards.
• Prefer landscape on very small phones if the header feels cramped.
• Theme label / username chip may hide on the smallest widths — Log out remains available.
• Use a stable connection; avoid multiple browser tabs of the same login if you can.

What captains cannot do

• No staff Run controls — you cannot start rounds, pause, terminate, or advance.
• No activating injects or changing inject preparedness / impact policy.
• No Prepare administration or Past Plays reports.
• No editing Scenarios / Injects / card definitions.
• No opening other teams’ Play tables.
• No uploading or changing the scenario image.
• No “Forgot password” for captain accounts — ask admin if credentials are wrong.
• You can use Messages (other captains anytime; facilitators/admin only when online) and Feedback.

If something fails with a permission toast, ask the floor facilitator or admin — it is intentional for workshop roles.

Quick round checklist

Match UI labels in the live app. Source: docs/guides-preview/captain.md.