Documentation

Copying and moving content between brands

How to reuse a knowledge base or documentation set in a second brand — Copy makes an independent duplicate that arrives entirely as drafts, Move hands the original over with everything it has learnt.

Where to find them

Open Brand → (your brand) → Knowledge, then the row's menu. Two entries sit there:

  • Copy to another brand…
  • Move to another brand…
Both stay greyed out — visible but not clickable — until your account has a second brand. There is nowhere for the content to go otherwise. A source always belongs to exactly one brand; there is no way to have the same one serve two.

Either entry opens the same dialog: you pick the destination brand, and the dialog spells out the consequence of the choice you made before you confirm it.

Copy — an independent duplicate

Choose the destination brand and, optionally, a different Name of the copy. Leaving the name alone is fine: the two live under different brands, so they cannot be confused.

The dialog states the important part up front — "Everything arrives as a draft":

"The categories and articles are copied across unpublished. Nothing appears on the other brand's public site and nothing is added to its AI until you publish it there — so this costs nothing until you decide it should."

What comes across:

  • every category and article (or documentation category and page), including how they are nested inside each other
  • the order you put them in and their slugs
  • for a knowledge base, the article images and its language and extra languages; for a documentation set, its language and its light and dark logos

What does not:

  • the published state — every item arrives unpublished, so nothing is served and nothing is indexed
  • ratings — the copy starts with none of its own
  • anything that links the two afterwards — they are separate from the moment the copy exists, and editing one never touches the other

Because nothing is indexed until somebody publishes it in the destination, a copy cannot push a free account over its indexed-item allowance by accident.

When it finishes you get a message saying "Copied — the copy is waiting in (the other brand) as a draft."

Move — handing the original over

A move is the original changing hands. The dialog warns "The original moves — this is not a copy":

"It becomes part of (the other brand) and leaves this brand entirely. Every article and everything the AI learned from them moves with it, at no cost. It arrives unpublished, so you choose when it goes live over there."

Nothing is re-read and nothing is re-indexed — everything the AI already learnt travels with it, and the move costs nothing. It arrives Hidden on the destination brand, deliberately, so that it can never silently displace whatever that brand is already serving.

If the thing you are moving is the one currently on this brand's public address, a second, red warning appears: "This is the knowledge base on this brand's public address — (this brand)'s public address will have nothing behind it until you publish something else there." Read it before confirming; after the move, visitors who open your address see nothing until you put something else on it.

When it finishes you get a message saying "Moved — it now belongs to (the other brand)."

Which one to choose

  • Copy when the two brands will drift apart — same starting point, different articles from here on.
  • Move when the content is simply in the wrong place and only one brand should have it.

There is no third option. Copy and Move are the supported replacements for the old arrangement where one knowledge base could be attached to several widgets at once; that relationship no longer exists.

Who can do it, and what can block it

Both actions need the Vex right, and also the right for the kind of content you are moving: Knowledge base for a knowledge base, Documentation for a documentation set. Without that second right the two menu entries stay greyed out, even when your account has a second brand.

The destination brand's allowance still applies: every brand holds at most five knowledge bases and five documentation sets (one of each on the free plan), so if the destination is already full, a copy is refused before a single article is duplicated, with an error naming the limit — and so is a move, since it adds one to the destination just the same. This particular error carries no button to the plan picker, because an upgrade does not raise a per-brand number; delete something on the destination brand first.