In our last post, the Fraud & Financial Crime and Customer Onboarding teams at the same fictional bank, Camundanzia Financial, each had their own Workspace inside one Organization in Camunda Hub. Both drew from the same Catalog. Every team that builds on Camunda adds to what the Center of Excellence (CoE) needs to govern.

The Catalog runs on approved building blocks. Its lifecycle lives in git, and the CoE can see how each asset gets used.

Approved building blocks, published once

Every Organization in Hub has one Catalog: a shared set of building blocks the CoE publishes for delivery teams. Connectors and element templates live here, including a Credit Bureau Pull and a Verify Identity (KYC) check. Sanctions & Watchlist Screen and Send Customer Notification are there too.

The Organization catalog in Camunda Hub. The CoE publishes approved assets, such as the Verify Identity (KYC) check, and delivery teams search and filter them by category and tag.

Shared resources in Camunda 8.9 let any developer “publish to org,” which leaves teams guessing which assets are the right ones. The Catalog works differently. The CoE decides what gets published, so delivery teams can reuse what’s there knowing it’s approved, versioned, and tested. Governance and version control, without slowing anyone down.

The Catalog is private to your organization. Camunda Marketplace is public.

Building gets faster

Delivery teams don't start from a blank canvas or a wiki page. They open the append menu in the modeler and drop in an approved building block from the Catalog search. Then they add their own steps before and after it.

The append menu in the modeler, with the Customer Onboarding team’s KYC check from the Catalog.

For the Customer Onboarding team, the KYC check is already there, approved, versioned and ready to use. Teams spend their time on what makes their process unique instead of rebuilding common steps. Review gets quicker too. The process still goes through review before production, but reviewers can focus on those unique steps, since the shared building block is already an approved version.

Lifecycle in git, usage in the Catalog

Your teams already trust the git workflow. Creation, review, and versioning stay there. Commit the implementation with its referencing element template, and CI deploys it to your environments and publishes it to the Catalog.

When a new version is published, projects on an older version get a notification to update. The update takes one click. Developers always see the latest version in the Catalog.

What the CoE sees

Asset usage shows which version every project runs, by Workspace and project: built-in observability for the CoE, not a report built later. APIs expose the same data for automations. That also limits the blast radius of a change. Before the CoE deprecates a connector, it can see which Workspaces and projects use it.

Across the fictional bank, six of seven assets are up to date. Verify Identity (KYC) is used by two Workspaces and two projects, all on the latest version. That’s reuse, made visible. Check Lending Policy shows an update available. One project in the Retail Lending Workspace is behind, and that team has already been notified.

The Asset usage view in the Organization catalog. Each asset shows its status, the number of Workspaces and projects using it, and how many are on the latest version. Check Lending Policy is the one asset with an update available.