> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wavecx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Child Demos

> Each child demo starts from the parent demo's content.

## Child Permissions

The Children tab on the parent demo controls what can and can't be changed at the child level. Use permissions to lock down the parts you want consistent across all versions while giving flexibility where it matters.

> [!TIP]
>
> Think of the parent demo as your master file. Build and maintain all your features and steps there, then use children to control which pieces each audience sees. This way, when something changes — a new screen, updated copy, a redesigned flow — you only need to update it in one place.

***

## **How Child Demos Work**

A child demo inherits all content from its parent — every feature, step, and piece of media. From there, you can:

* **Adjust features:** Hide features that aren't relevant to the child's audience. The content stays in the parent and can be re-enabled at any time.
* **Adjust the layout:** Change the desktop or mobile layout, toggle components ON or OFF, or apply a different preset — independently from the parent.
* **Customize settings:** Modify the child's name, audience, branding, and other settings without affecting the parent.

> [!NOTE]
>
> When you edit features or steps in the parent demo, those changes automatically flow down to every child. This makes the parent your single source of truth — update once, and all children stay current.

***

## Child Demo List

Once you have created Child Demos, they will then show as a list. The list itself shows each child's **Name**, **Last Updated** (and by whom), **Tags**, and a **Link** to open it.

### **Selecting one or more child demo reveals:**

* **Archive / Unarchive —** Move children out of (or back into) the active list without deleting them.
* **Delete —** Permanently removes archived children.
* **Duplicate As Demo —** Turns selected children into brand-new, independent demos.
* **Duplicate As Variant —** Creates new children with the same starting content, still tied to this parent.
* **Download —** Downloads the selected children.
* **Send Invitation —** Sends a direct link to the selected children by email and/or SMS.
* **Export Feedback —** Exports feedback responses collected from the selected children.
* **Deselect All —** Clears your selection.

***

## Permissions

Choose which specific fields children of this demo are allowed to override. Anything you leave locked stays in sync with the parent automatically — update the parent, and every child picks up the change.

* **Unlock All or Lock All —** If either are selected, it will unlock or lock all individual settings across the child demo. *This includes Settings, Demo Content, Layout and Launch permissions.*
* **Selecting an item —** Choose precisely what can be edited. Whether it is an individual feature, step, text field, or any other option inside the parent demo.

***

## **Common Use Cases**

Most teams use child demos as focused snippets of a larger parent:

* **Feature-specific demos —** A parent covers the full app, and each child shows just one feature — Deposits, Transfers, Bill Pay, etc. Great for embedding on targeted pages or sending in campaigns.
* **Audience variants —** Same walkthrough, different branding or layout for customers vs. employees, or for different product tiers.
* **Training modules —** Break a comprehensive training demo into smaller, digestible segments that link back to the same source content.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.