Manage sub-scenarios and their access

A sub-scenario explores a variant from an existing scenario. Its direct source is that parent, so applying the child transfers changes to the parent rather than directly to real data.

Create a branch from a scenario

1. Open Data context and find the active, ready parent you can access.
2. Open its Actions > New sub-scenario.
3. Check Branched from and enter a name and optional description.
4. Choose Visibility explicitly. For Private, select the intended members under Share with. Optionally delegate application to Editors under Can apply.
5. Click Create, wait for preparation and select the ready child.
6. Check the child's name in the context selector before editing.

Creation requires permission to create scenarios and an available place in the shared quota. Reading the parent is sufficient to create a child; applying that child later requires management access to the parent.

Choose the audience for each branch

The creation dialog defaults to Organization, even when the parent is private. A child does not automatically inherit its parent's confidentiality. Check its audience before copying the parent's data.

Access to a child does not automatically grant access to its parent, or the reverse. Organization administrators retain access to private scenarios. Existing permissions still govern the assets and visualizations inside each copy.

Share access and delegate application

Scenario managers control sharing. A manager is an Editor or higher who created the scenario, or an organization Administrator or Owner.

1. Open the scenario's Actions > Share.
2. Set Visibility. For a private scenario, select its audience under Share with.
3. Under Can apply, select the Editors allowed to apply its changes.
4. For a private scenario, check Share with: selecting someone under Can apply also adds them to this audience.
5. Click Save.

Removing someone from a private scenario's shared members also removes their application delegation. The creator and administrators retain access.

Can apply grants application, subject to destination data permissions. It does not grant renaming, sharing, conflict resolution, resynchronization, archiving or undo. A child still requires management access to its parent before application.

Use comparison and resynchronization to refresh a branch. Comparing a child with real data does not change its parent.

Archive, reactivate or delete

Choose the lifecycle action from the scenario's Actions menu. Read its confirmation and check any child branches before proceeding.

Action	Result and conditions
Archive	Removes the working copy, keeps changes for reactivation and frees an active place. Active children block archiving.
Reactivate	Rebuilds an archived scenario from its current source and replays its changes. Requires creation permission, quota and management access; a parent must be active and ready.
Complete application	Transfers the remaining eligible changes, archives the scenario with the Fully applied label and attaches open children to its source. See application results.
Delete	Permanently removes the scenario, its copy and change history. Active or archived children block deletion. Application reports are retained separately.

To reactivate, find the archived scenario in the selector and choose Reactivate on the right of its row. Read the confirmation, wait for preparation, then inspect conflicts before returning to work. Reactivation uses the source's current data, so the copy may differ from when it was archived.

Before deleting a parent, resolve its active and archived children. Already applied or abandoned descendants can be removed with it. Read the confirmation as a branch operation, not merely removal of a name from the selector.

Unchecking Accept during review leaves the change in the scenario. To withdraw a change, edit the affected data in the scenario itself, or, for a conflict, choose Keep the source. Archiving or deleting acts on the whole scenario.

Handle inactivity and organization settings

After 90 days without activity, a scenario can be automatically archived when its context is checked. Consultation counts as activity; only counting edits gives an incomplete picture. This is not a promise of closure at a precise time on day 90.

If an active child prevents automatic archiving, Boldo asks you to archive or apply the children first. Review the branch with its manager rather than repeatedly opening the parent. Children are not automatically deleted to clear this condition.

An administrator can manage activation under Organization > Scenarios > Activation > Manage. Set Enable scenarios, then Validate. The plan and each member's creation permission still apply.

Disabling scenarios makes their contexts unavailable and returns the client to real data. It is not equivalent to deleting each scenario. The administration list also helps check active or preparing scenarios against the organization's quota.