Requirements

Before you can deploy a global package, it must be fully prepared and approved in the editor tenant. A global package namespace must be created in CloudSuite Portal, and at least one package version for that namespace must exist with a successful build.

In WFM, you must use Configuration Management to associate all required functional objects with that namespace so that CSP can export the correct contents. From CSP, you then create and export the package version for that namespace. That version must be entitled to the target customer, activated, and, in most governance models, validated in a non‑production tenant, with any prerequisite global packages already deployed.

You also need the right access and deployment context in place. Only users or Cloud Ops staff with the appropriate CSP roles should perform deployments, and they must identify the correct source tenant, target tenant, namespace, and package version. Any package parameters defined for the global package must be understood and agreed in advance, because deployment will require entering suitable values for the target tenant. Finally, the target tenant must already have WFM provisioned and in a valid state to receive the package, and the WFM validation step must pass without blocking errors before deployment can proceed.