Step 3 — Location

Which space the copies land in, and where they sit in the page tree.

v10.2.0 — Latest Runs on Atlassian Atlassian Forge Confluence Cloud

Step 3: Location — set where the copies are created — Choose where the copies land.

Where the copies land. The destination space does not have to be the space the source page lives in — cloning a template out of one space into another is the normal case, not an edge case.

Pick the destination Space.
Choose how the copies are organised — the three options are below.

The clone summary now shows the full destination. When it reads correctly, click Create n pages — the button names the number, so you get one last chance to notice if it says 25 when you meant 3.

Placement options

On Step 3 you choose how the copies are organised. There are three options, and the difference is where they sit in the page tree:

As a child of an existing page — copies become child pages under a parent you pick. A Parent page search appears below; the parent has to already exist.
As parent pages in [Space] — copies sit at the space root with no parent above them. Use this when each copy is a top-level document in its own right.
As child pages of a new parent — the app creates one new parent page first, then files every copy underneath it. You give the parent its own title in New parent page title. This is the tidiest option for a batch that belongs together, because it leaves the space root untouched.