Copy or move a knowledge base to another brand

Updated August 13, 2026

Why you cannot just share it

A knowledge base — and a documentation set — belongs to exactly one brand (see what a brand is in Yaplet). There is no way to attach the same one to two places at once. Content is stored and indexed once, for its owner.

So if you want the same articles somewhere else, you have two choices: copy them, or move them.

Where the two actions live

Go to Brand → Knowledge, find its row in the Knowledge bases & documentation group and open its three-dot menu. Two items sit near the bottom:

  • Copy to another brand…
  • Move to another brand…

Both stay grayed out until your account has a second brand — they are not hidden, so you can see they exist. Both open the same dialog, which asks which brand you mean and then spells out what will happen before you confirm.

Copy — a duplicate that starts as drafts

Copying duplicates every category and every article: the nesting, the ordering, the language, the translations and the article bodies. You are asked what to name the copy; leaving the original name is fine, because the two live under different brands and cannot be confused.

The important part is what does not happen. As the dialog puts it: "Categories and articles arrive unpublished. Nothing shows on the other brand's public site and Yaplet does not learn from it there until you publish it — so it costs nothing until then." In practice that means:

  • No public page appears the instant you click Copy.
  • Nothing is indexed, so copying teaches Yaplet nothing until you publish it there.
  • Article ratings start fresh — they belong to the copy, not to the original.
  • From that moment the two are independent. Editing one never touches the other.

Move — the original changes hands

Moving is not a duplicate. The knowledge base leaves this brand entirely and becomes part of the other one, taking its articles and everything the AI has already learned from them. Nothing is re-read and nothing is re-indexed, so it costs nothing and takes no time.

It arrives as AI only on the destination — not on its public site. That way it cannot silently displace whatever that brand is already serving on its own web address — putting it up is a separate decision, made over there.

The warning worth reading twice

If you move the knowledge base that is currently on this brand's public web address, that address will have nothing behind it afterwards. Visitors who open it see an empty page, and the widget's Help tab has nothing to show. The dialog warns you about this before you confirm: "This is on this brand's public site", followed by a note that the brand's public address will have nothing behind it until you publish something else there.

If that is you, decide what goes up in its place first, and put it there straight away afterwards — on Brand → Knowledge, using Show at your-address.yaplet.help in another row's menu. For how several knowledge bases behave inside one brand, see Run more than one knowledge base.

Did this article answer your question?