Overview
Bind a compatible workspace application to PROJECT_CATALOG so products can be linked to projects.
Prerequisites
Permissions required
Steps (5)
-
1
Open outbound integrations
Open ProductCatalog Integrations and choose the project catalogue dependency.
Tips
Validation
Success criteria
-
2
Discover a compatible provider
Find an installed app that advertises the project.json handler and the projects.list capability.
Tips
Validation
Success criteria
-
3
Verify provider authorization
Probe the provider and confirm ProductCatalog is authorized for projects.list.
Tips
Validation
Success criteria
-
4
Bind the provider
Save the selected application as the PROJECT_CATALOG provider.
Tips
Validation
Success criteria
-
5
Link a product to a project
Use the project picker while editing the product and save the normalized project reference.
Tips
Validation
Success criteria
About this guide
ProductCatalog is a workspace-local catalogue authority for physical and digital products. Create products with canonical identity, SKU, pricing and lifecycle state, then extend them with type-specific attributes, media, options and option values.
Organize the catalogue with hierarchical categories and curated collections. Attach discounts, offers, loyalty programs, shipping promotions and referral programs directly to products or inherit them through categories and collections. Products can also retain normalized references to projects supplied by a compatible workspace project-catalogue provider.
ProductCatalog exposes governed integration contracts for trusted workspace apps and external systems. Handler and RCP calls use explicit per-application operation grants, ContextResolver exposes source-owned product context, EventBus publishes catalogue changes, and HMAC v2 Bridge credentials provide scoped external access with replay, rate, network, rotation and revocation controls.