diff --git a/modules/dynamic-plugins/proc-export-third-party-plugins-rhdh.adoc b/modules/dynamic-plugins/proc-export-third-party-plugins-rhdh.adoc
index 379f0bb2b3..6570310926 100644
--- a/modules/dynamic-plugins/proc-export-third-party-plugins-rhdh.adoc
+++ b/modules/dynamic-plugins/proc-export-third-party-plugins-rhdh.adoc
@@ -7,6 +7,18 @@ To use plugins in {product}, you can export plugins as derived dynamic plugin pa
 
 .Prerequisites
 * The `@red-hat-developer-hub/cli` package is installed. Use the latest version (`@latest` tag) for compatibility with the most recent features and fixes.
++
+[NOTE]
+====
+Use the `npx @red-hat-developer-hub/cli@latest plugin export` command to export an existing custom plugin as a derived dynamic plugin package.
+
+You must use this command when you have the source code for a custom plugin and want to integrate it into {product-very-short} as a dynamic plugin.
+
+The command processes the plugin's source code and dependencies and generates the necessary output for dynamic loading by {product-very-short}.
+
+For an example of using this command, see xref:proc-example-custom-plugin-installation_assembly-install-third-party-plugins-rhdh[Example of installing a custom plugin in {product}].
+====
+
 * Node.js and NPM is installed and configured.
 * The {plugin-type-name} plugin is compatible with your {product} version. For more information, see link:https://github.com/redhat-developer/rhdh/blob/main/docs/dynamic-plugins/versions.md[Version compatibility matrix].
 * The {plugin-type-name} plugin must have a valid `package.json` file in its root directory, containing all required metadata and dependencies.