Scenario Flow
What this screen is for
A scenario is a group of questions written for one situation — a security incident, a compliance audit, a migration plan — and this screen lists the questions of one scenario, numbered in the order the catalogue gives them. The number is a position, not a step: each question is run on its own, in any order, and nothing is carried from one to the next. The screen says so itself, under Independent Questions.
Every question here is a read. The guarantee that nothing in the Hub changes state, and the rules deciding which questions you are shown, are on the Hub page:
The scenario's name and description are the console's and follow your language; the question titles come from the catalogue and are in English whatever the language.
What must exist first
The scenario must hold at least one question listed for you: offered, blocked, or waiting for a tenant. Otherwise the page shows This scenario is not available, with a button back to the Hub — and it shows exactly the same for a scenario that does not exist, so that a link cannot be used to learn which scenarios hold what. The count badge at the top counts the questions you can run in the current scope, not the scenario's whole set.
On the platform, the page carries the same Scope control as the Hub, with the scope you chose there, and Back to Hub keeps a change made here.
Decisions you make here
Choosing a question
An offered question's card opens its page on click, with the priority band, category and description to choose by; the page then offers Back to this scenario. A blocked question's card carries the notice explaining why it cannot run, such as the missing authority by name, and does not open.
The questions that need a tenant are not cards: they are listed after the others in the collapsed Requires entering a tenant (N) section, whose control enters the chosen tenant and brings you back to this scenario inside it. What to do about each is described on the Hub page.
Choosing an order
Any order. Running one question neither unlocks nor changes another, and an answer is never passed into a later question's inputs: if two questions ask for the same key or user, you enter it twice.
How it relates to other screens
Each card opens the question's own page, where the inputs are given and the answer read:
Every question run from here is recorded like any other: