Data marketplace governance: what changes for IAM and access teams?

TL;DR: Fewer than 25% of organizations can demonstrate measurable impact from data investments, and Collibra’s updated Data Marketplace is aimed at making governed data products easier to discover, evaluate and request through business categories and curated access flows. The bigger shift is governance moving closer to consumption, where trust, context and access are embedded at the point of use rather than left to technical catalogs alone.

NHIMG editorial — what this means for NHI practitioners

By the numbers:

• Up to 20 categories can serve as primary navigation hubs.

Questions worth separating out

Q: How should teams govern access to data products in a marketplace model?

A: Teams should govern data products as reusable access objects with named ownership, approval routing and review cadence.

Q: Why do data marketplaces matter to identity and access teams?

A: Data marketplaces matter because they move access governance closer to consumption.

Q: What do organisations get wrong when they treat a data catalog as a marketplace?

A: They assume discovery is enough.

Practitioner guidance

• Map marketplace objects to governance owners Assign a named business owner, technical steward and approval path to every high-value data product so requests do not stall in ambiguity and certifications stay current.
• Use business categories as access decision support Organise the landing experience around business domains that match how users request data, then keep approval logic tied to the underlying entitlement model.
• Attach evidence to every request workflow Ensure access requests move through Jira or ServiceNow with approvals, certification status and ownership details preserved for audit and recertification.

What's in the full announcement

Collibra’s full blog post covers the product detail this post intentionally leaves for the source:

• The updated landing page structure and the administrator controls used to tailor business categories, featured assets and visible metrics.
• The product-specific workflow details for adding data products to shopping lists and routing requests through Jira or ServiceNow.
• The hybrid-model guidance for organisations that still need to surface reports and datasets alongside data products during transition.
• The preview and product premiere context for teams that want to evaluate the experience before standardising on the new marketplace model.

👉 Read Collibra’s update on the new Data Marketplace experience →

Data marketplace governance: what changes for IAM and access teams?

Explore further

View Full Forum →  |  NHI Foundation Course →