Skip to main content

Marketplace assets and authority boundaries

N
Written by Niyaz

Marketplace catalogs

The Hub Tools page includes App Store and Platform Registry. The catalogs describe marketplace assets that you may adopt. The installable mini-app catalog serves your store. The platform-capability catalog covers data sources, events, and contracts. Use these catalogs to discover and review listings, assess compatibility, request entitlement, plan installation, and retain marketplace interaction records. An asset is suitable for discovery only when it is versioned, attributable, and governed.

Tools page with App Store and Platform Registry marketplace links.

A listing is not permission

A marketplace listing communicates that an asset has been approved for presentation, but it does not decide whether you may use the asset. A listing does not grant entitlement, activate an asset in production, permit customer-data access, confirm support acceptance, or complete a commercial agreement. Keep certification, entitlement, installation, and runtime activation as separate decisions.

Evaluate compatibility and access

Assess compatibility against the explicit versions of the platform, its dependencies, and the target environment. Keep third-party code isolated, declare its permissions, and restrict its outbound access. Confirm partner intellectual property, contract terms, billing records, certification decisions, runtime activation, and customer-data permissions outside the catalog.

Respond to suspension or recall

When an asset is suspended or recalled, prioritize customer protection and preserve its historical evidence. Do not delete historical asset evidence because the asset is suspended or recalled.

Related

Did this answer your question?