Walkthrough

Introduction

Figure 1 depicts the workflows available in the Immuta Marketplace. This walkthrough will guide you through these steps.

Some of these steps are performed by different user types in Immuta, so this walkthrough is organized by Marketplace user type.

Requirements

See the Marketplace app requirements page.

Governance and user admin users

The data sources that are exposed through your data products are sourced from a domain; so in order to publish a data product, you must have at least one domain with at least one data source in it. Any user with the Immuta GOVERNANCE permission is able to publish data products in the Marketplace app using any domain. However, this job can be delegated by creating data product managers. You create data product managers by giving them the Manage Data Product permission in a domain.

As shown in Figure 2, creating a domain and assigning data sources to it is handled by a user with GOVERNANCE permission. Assigning the Manage Data Product permission is handled by a user with USER_ADMIN permission.

These actions are completed in the Governance app, not the Marketplace app.

Data product manager user

This user is able to publish the data products, manage their metadata, and manage request forms. As mentioned above, to be a data product manager, one must have the global GOVERNANCE permission or the domain-specific Manage Data Products permission in a domain.

From there, data product managers are able to publish and manage data products, from their domains, as depicted in Figure 3.

However, the first step in creating a data product is ensuring that the data sources that make up the data product are contained in the domain where you have the Manage Data Product permission.

Making data sources available in a domain

See the Setting up domains for Marketplace page for details about how to automatically have data sources be assigned to domains.

Data consumer user

A data consumer can be anyone with a login to the Immuta. They can visit the Marketplace app, search for data products, and request access, as shown in Figure 4.

Data steward user

The data stewards are tasked with making determinations on Marketplace access requests, the final step in the workflow depicted in Figure 5.

Users with the global GOVERNANCE permission or the domain-specific Manage Data Product permission in the domain are the default data stewards in a request form for the data product. However, you can assign any user, group, attribute, or permission as the data stewards while creating the data product or request form.

When an access request is made that requires approval, that request will appear as pending in the Marketplace, signaling a determination is required. The data steward can make the determination by approving, denying, or temporarily approving it it with a reason, and if approved, Immuta will automatically provision the access, completing the workflow.

Soon the Marketplace app will support notifications (email, Teams, Slack, webhooks) which will allow the users assigned to make an determination on a request to be notified of this, as well as the requestors notified when a determination has been made.

Optional considerations

• Consider branding the Marketplace app with your own logo and colors, to give it the look and feel of your company.

• If you would prefer that data consumers discover data products in your existing catalog, that is possible to configure. The Marketplace app is built in a way so it can present the access request page to the consumer via redirects from your catalog.