Shopping improvements for Data Marketplace (in preview)

November 12, 2026

Shopping improvements for Data Marketplace (in preview) give you more control over which assets users can request access to and more flexibility in how they send requests. Users can request access directly from an asset or add multiple assets to their data basket and send a bulk request at checkout.

You can configure the shoppable scope, request model, workflow, and domain in which Data Usage assets are created. This topic describes the new features and explains how to configure them.

Shoppable scope

You define which assets users can request access to based on asset type, status, and organization on the Shoppable assets tab in Data Marketplace settings. The shoppable scope is independent of the Data Marketplace scope. This means you can:

• Show Data Products in Data Marketplace and let users request access to individual Data Product Port assets.
• Show reports that everyone in your organization can already access, without a request button.
• Use statuses to exclude Data Product Port assets that are still in development or used for versioning.

Users see the request button on an asset if at least one asset type on the Asset types and status tab includes the asset's type and status. For example, if Report is listed with inheritance and the Accepted status, and BI Report is listed with the Candidate status, BI Report assets with either status are shoppable.

If users don't see the Request access or Add to Data Basket button on an asset or in its preview, check the following:

• On the Shoppable assets tab:
  • The asset's type and status are included on the Asset types and status tab.
  • The asset belongs to a community or domain selected on the Organization tab.
• The Add to Data Basket action is pinned to the asset type's layout.
• Users have View permission on the Data Usages domain selected on the Requesting access tab.

Users can request access to any asset in the shoppable scope from Catalog, the asset page, or Collibra Maestro, even if the asset isn't shown in Data Marketplace.

Access requests for Data Product Port assets

A Data Product asset can have a mix of Data Product Port assets: some that users can request access to through Data Access, some that require a workflow, and some that aren't shoppable, such as obsolete ports.

When users open the preview of a Data Product asset, they see its Data Product Port assets. To request access, users click Request access or Add to Data Basket in the Output Ports Viewer widget. They can also request access from the Data Product Port asset preview or its asset page.

Request model

Most access requests are for a single asset, such as a Data Product Port asset. By default, users request access directly from an asset and proceed to checkout. If you select Enable bulk access requests using the Data Basket, users add assets to their data basket instead and send a single request for all of them at checkout.

Both request models, direct and bulk requests, create a Data Usage asset and use the same workflow. With direct requests, assets show Request access. With bulk requests, they show Add to Data Basket.

Access request workflow

You select the workflow that handles access requests on the Requesting access tab in Data Marketplace settings.

You can use the system access request workflow or a custom resource workflow.

• Use the system access request workflow
  • The system workflow supports Data Set, Report, and Data Product Port assets. It handles other asset types in the shoppable scope the same way as Report assets, so you don't need to update the workflow when you add asset types.
  • You can't modify the system workflow, and requesters and approvers don't need a Contributor license. Each requested asset must have an Owner; otherwise, the request ends.
  • For Data Set assets, an inherited Owner is enough. For all other asset types, including Data Product Port assets, the Owner must be assigned directly on the asset.
• Use a custom resource workflow instead: A workflow you create that meets the requirements described in Configure requesting access. To start from a template, download the Data Marketplace Access Request Workflow from Collibra Marketplace and customize it.

Data Usages domain

On the Requesting access tab in Data Marketplace settings, you can choose a domain of the Data Usage Registry type in which new Data Usage assets are created, instead of using the out-of-the-box Data Usages domain. This means you don't have to make the Business Analysts Community visible to everyone. You can select one domain for all new Data Usage assets.

In a custom workflow, you can also move Data Usage assets to another domain. For example, you can move them to a domain that inherits responsibilities for an approval flow or to a domain with restricted View permissions after approval.

The Access requests page shows all of a requester's Data Usage assets, regardless of their domain.

Data Usage assets are included in the Insights Data Access reporting layer.

Other improvements

• A refreshed request form with clearer field labels and a date selector for the access period, with presets such as six months or custom start and end dates.
• Notifications by email and in the notification center when a request is rejected or access is granted.

Default settings

When you enable Shopping improvements for Data Marketplace (in preview), the settings on the Shoppable assets and Requesting access tabs in Data Marketplace settings have the following default values.

• New environment: An environment where Data Marketplace has never been configured. Collibra applies the new default settings.
• Existing configuration: An environment where Data Marketplace was configured before you enabled Shopping improvements for Data Marketplace (in preview). Collibra preserves the existing behavior as much as possible to minimize changes for users.

Setting	New environment	Existing configuration
Request model	Direct requests	Enable bulk access requests using the Data Basket is selected.
Workflow	Use the system access request workflow	Use a custom resource workflow instead, with the previously used workflow preselected.
Shoppable scope	Data Product Port, Data Set, and Report, including child asset types, with all statuses, across your entire organization	The Data Basket configuration is not carried over. You must configure it again.
Data Usages domain	Out-of-the-box Data Usages domain	Out-of-the-box Data Usages domain

Enable Shopping improvements for Data Marketplace (in preview)

Enable Shopping improvements for Data Marketplace (in preview) to configure which assets users can request access to and how they send requests.

Prerequisites

• The Data Marketplace experience is enabled.
• You have a global role with the System administration global permission.

Steps

1. Go to Settings > General > In Preview.
2. Enable Shopping improvements for Data Marketplace.
   In Data Marketplace settings, the Shoppable assets and Requesting access tabs are shown instead of the Data basket tab.
3. Review the shoppable assets scope. For more information, go to Configure shoppable assets.

You can disable the preview at any time. When you disable it, the Data basket tab is shown again instead of the Shoppable assets and Requesting access tabs.

Configure shoppable assets

Configure which assets users can request access to.

Prerequisites

• You have a global role with the System administration global permission.
• Shopping improvements for Data Marketplace (in preview) is enabled.

Steps

1. Go to Settings > Data Marketplace > Shoppable assets.

2. Configure the shoppable asset types and statuses:

   1. Click the Asset types and status tab.
      The shoppable asset types are shown with their statuses. Inheritance is shown for asset types that include their child asset types. By default, the shoppable asset types are Data Product Port, Data Set, and Report.

   2. To add an asset type:

      1. Click Add asset type and select the asset type.
      2. To include child asset types, select the Include child asset types checkbox.
      3. In the Statuses list, select the statuses that make assets of this type shoppable.
      4. Click Save.

   3. To edit an asset type, click the Edit icon next to it.
      The edit dialog box appears.

      1. In the Statuses list, select the statuses that make assets of this type shoppable.
      2. To include child asset types, select the Include child asset types checkbox.
      3. Click Save.
   4. To stop using a default asset type, disable the switch next to it. To remove an asset type that you added, click the trash icon.

3. Configure the shoppable organization:

   1. Click the Organization tab.
      By default, the shoppable scope covers your entire organization, with no communities or domains selected.
   2. Select the communities and domains whose assets you want to make shoppable.
4. Click Save.

Configure requesting access

Configure how users request access.

Prerequisites

• You have a global role with the System administration global permission.
• Shopping improvements for Data Marketplace (in preview) is enabled.
• Optional: A domain of the Data Usage Registry type exists if you don't want to use the out-of-the-box Data Usages domain.
• Optional: If you want to use a custom workflow, the workflow is deployed as a resource workflow that runs on Data Usage assets in the Candidate status.

Steps

1. Go to Settings > Data Marketplace > Requesting access.
2. By default, users request access directly from each asset. To let users add assets to their data basket and request access to multiple assets in a single request, select the Enable bulk access requests using the Data Basket checkbox.

3. Adding an asset to the data basket or requesting access creates a Data Usage asset in Candidate status, stored by default in the Data Usages system domain. To change the domain:

   1. Select Change data usages domain.
   2. In the Domain field, select the domain in which new Data Usage assets are created. You can select any domain of the Data Usage Registry type.

4. Select the workflow that handles access requests:

   • To use the system workflow, select Use the system access request workflow.
   • To use your own workflow, select Use a custom resource workflow instead, and then select the workflow from the list.
     Note 

     If your custom workflow assigns tasks to the requester, the requester needs a Contributor license.

5. Click Save.

If you already use Data Marketplace

After you enable Shopping improvements for Data Marketplace (in preview), verify the following settings:

1. Shoppable scope: Configure the shoppable scope. Your previous data basket asset types aren't carried over.
2. Access request workflow: Make sure the correct workflow is selected. If the workflow list is empty, Collibra didn't identify your existing workflow. Select it manually.
3. Bulk requests: Clear the Enable bulk access requests using the Data Basket checkbox to let users request access directly.

What's next

• Your access requests
• Using the data basket in Data Marketplace