Clone a Workspace

Why clone

A tuned vault — the component library you trust, the playbooks that actually fire, a scope structure that matches how you work — is a head start. Cloning copies it into a fresh workspace so the next engagement begins from your best state, not from zero.

What you can take with you

Open Workspace Settings → Clone Workspace. You choose which parts come along:

• Programs & Assets — platforms, programs, assets, and their notes and observations.
• Components — the component library.
• Playbooks — the threat library, with requirements and yields.

All three are selected by default; deselect what you don't need.

Cross-references are handled for you: if a cloned link points at something you did not select, the reference is pruned cleanly — never left dangling, never silently pulling in things you excluded. The whole clone runs as a single operation, so a half-cloned workspace cannot happen.

When to clone

• New engagement, same playbook. Keep the library and the team's playbooks; bring a fresh scope.
• Client templates. Maintain a well-curated base workspace and branch it per client.
• Experiments. Duplicate before a big restructure; the original is untouched.

What's next

• Manage Your Scope — shape the fresh clone.
• Share and Collaborate — bring the team in.