Journeys

A journey removes the “what do I do first?” problem. Instead of staring at an empty domain and assembling the right libraries, assessments and tasks by hand, you pick a ready-made template, apply it to a domain, and work down a prescribed list of steps. The objects the programme needs are created for you, and each step links straight to the screen where the work happens.

Where to find it

Overview → Journeys in the sidebar.

Templates and journeys

Two objects are at play, and they mirror the framework-and-audit pattern used elsewhere in CyberGuard:

A template (internally a preset) is the reusable definition. It bundles a set of starter objects and an ordered list of steps. Templates are versioned and usually arrive as libraries, though they can also be authored locally.
A journey is one application of a template to one domain. Applying the same template to three domains gives three journeys, each tracking its own step statuses and notes independently.

The page is split accordingly: Recently active journeys at the top, each with a progress ring and an x of y steps completed line, and Available Templates below. Templates carry region tags so you can narrow a long catalog to the ones relevant to where you operate, and expanding a card reveals what it will create — how many compliance assessments, risk assessments, EBIOS RM studies, task templates, perimeters, assets, entities and so on.

If the catalog is empty you will see No presets available. Upload a preset library to get started. — load one from Libraries first.

Starting a journey

Press Start a journey on the template card. The dialog opens on Choose where to create the journey objects.
Pick the target: Create a new domain and type a Domain name, or Use an existing domain and select one.
Decide on Create underlying objects. Leave it on and the template scaffolds its assessments, assets and other records. Turn it off and the journey is created as a pure checklist — useful when the objects already exist and you only want the guidance.
Decide on Adjust menu and modules. This applies the feature flags the template expects, so the sidebar matches the programme’s scope. You can change any of them later under Extra → Settings → Feature flags. The option is unavailable if you cannot change feature flags yourself.
Confirm. You land directly on the new journey.

Starting a journey requires permission to load libraries in the target domain, so it is typically an administrator or domain manager action.

Working the steps

Each step has a title, a description and — where it applies — a link to the object or screen it concerns. Steps move through four states, driven by the buttons on each row:

State	Set with
Not started	The initial state, or Reset
In progress	Start
Done	Mark as done
Skipped	Skip

Journey Progress at the top rolls the states into a single bar. Show descriptions and Hide descriptions toggle the explanatory text when you want a tighter checklist, and Edit links lets you repoint a step at a different object — handy when you turned off object creation and are wiring the steps to records you already had. A Stats panel summarises what the journey’s domain now contains: assets, risk scenarios, applied controls, compliance progress.

Journeys can be renamed, and deleted when the programme is over. Deleting a journey removes the checklist, not the objects it created.

Upgrades

When a newer version of a library-backed template ships, journeys derived from it show an Upgrade available badge. Upgrading re-applies the newer template while preserving your own state — statuses and notes survive on every step that still exists in the new version.

Libraries — where templates come from.
Domains — the scope a journey is applied to.
Audits — the assessments a template usually scaffolds.
Feature flags — the switches the Adjust menu and modules option sets.