Overview
Bind a provider-neutral project catalogue and retain normalized project references on products.
Problem
Products or listings may belong to projects that are owned by another workspace application.
Solution
Configure a compatible PROJECT_CATALOG provider and use its projects.list capability from the ProductCatalog project picker.
How it works
ProductCatalog stores normalized project reference metadata while the project provider remains authoritative for project management.
Who is this for
Catalog Manager
Project Operations
Expected outcomes
- Project linkage without duplicating project management
- Provider can be changed without hardcoding a specific project app
Key metrics
Security impact
- Project provider binding and normalized project reference metadata · PII: depends on catalogue attributes, media, and metadata supplied by the workspace
Compliance
- Workspace permissions, Products Core grants, trusted execution, transport authorization, and secure file boundaries.
Availability & next steps
Pro
Enterprise