Keep translations attached to the intended KB article so a language update does not accidentally create another page or replace the main version. Use the language fields supported by your installation.

Confirm content permissions

Use a dedicated content connection with a Write ceiling, the required content area and staff permissions. The separate read-only override must permit the intended write. The bound administrator needs Manage Knowledgebase in its administrator role. A connection limited to selected clients cannot operate on the shared knowledge base.

WHMCS uses language names such as german, rather than locale codes such as en_us. Use a language installed and accepted by this installation; the hub validates the supplied language and can return the accepted names when it rejects one.

Add the translation to the existing article

1. Read the main article and note its ID, categories and access.
2. Prepare and review the translated title and body.
3. Ask the assistant to use Add a knowledge base article with translation_of set to that main article ID, the accepted language, and the translated title and body.
4. Read the main article again and inspect its returned translations.
5. Check the requested language in the native client view.

The translation belongs to the main article rather than becoming another separately categorised page. Do not create an unrelated main article merely because the title is in another language. The translation tool can update an existing entry for the same main article and language, so check whether that version already exists before replacing it.

Revise the right language

Use Edit a knowledge base article with the main article ID and the intended language when revising a translation. Omitting the language targets the main text instead. Keep access, categories and tags out of a translation-only update unless the main article’s shared settings should also change.

Check the final language and access

Read the article after the change and compare the requested language text, earlier versions, categories and audience. Language editing does not authorise broader publication. Review the native page in the intended language too; a saved entry is not proof that a language selector or template displays it as expected.

If an error occurs, read the existing article and language entries before retrying. Do not delete the main article to remove a mistaken translation attempt, because that would affect more than the one language version.

See the PD MCP Hub WHMCS guide for related tasks, or explore PD MCP Hub.