Publish to the Marketplace

Publishers distribute qualified packages through the Marketplace or retain them in a private registry. Sharing or selling a release changes its distribution and entitlement rules, not the platform's security and compatibility requirements.

Listing and documentation

A listing identifies the publisher, stable package ID, capability, supported release line, dependencies, requested permissions, licensing, support and canonical documentation. Documentation covers the package itself, including when it is used outside its original industry solution.

Compatibility declarations

Declare provided and required capabilities, schema/interface contracts, supported runtime profiles, conflict and replacement rules, and migration constraints. A version range alone does not prove compatibility. Qualification includes contract and composition checks against the target installation.

Signed installation context

When an authorized administrator opens the Marketplace from a deployment, the platform supplies a purpose-limited installation profile. The Marketplace distinguishes installed, available, compatible, blocked and upgradable packages using declared requirements and the resolved lock. It does not require access to customer business evidence to make that comparison.

Documentation ownership

Package documentation owns its agents, workflows, models and screens. Solution documentation links packages and explains joint workflows. Shared services remain in Platform Documentation; SDK procedures remain in Developers. Bidirectional package/solution references are generated from composition metadata.

Publishing and deployment

A publisher submits signed artifacts and qualification evidence for the applicable publication controls. Publication and deployment are separate operations: listing a release does not install it in customers' environments. Customers review the installation plan, entitlements, permission changes and migrations before promotion.

Extensions

An enriching package declares its host dependencies and contribution points, retains its own publisher identity and documents removal effects. It never overwrites another publisher's original artifact. Private customer overlays do not require Marketplace publication.