In Blindata Marketplace, a Consumer is a user who requests access to data products through the marketplace. Consumers can browse available data products, submit access requests with required justifications, and manage their existing access permissions. When requesting access, it is recommended to provide a clear business case and intended usage details.

To request access to data products in Blindata, you must have both the DATA_PRODUCT_VIEWER permission (to view data products) and the MARKETPLACE_VIEWER permission (to access the marketplace). Users with both permissions can create access requests for themselves or on behalf of others using the access request modal—a guided, three-step process designed to facilitate requests for access to the output ports of available data products.

Discovering Data Products

To discover data products of interest, consult the Data Catalog. Here, you will find an overview of available data products, conveniently grouped by domain for easier navigation. Use the search bar to locate specific data products by name or relevant keywords, and refine your results by applying filters based on data product properties, such as domain or alignment (source-aligned, consumer-aligned, or aggregated).

Once you identify a data product, visit its detail page to review general information, description, dependencies, policy metrics, data quality highlights, responsibilities, input/output ports, documentation, custom properties, and—most importantly—the output ports where access can be requested.

For more information about data products, refer to the Data Product Catalog page .

How to Create an Access Request

After reviewing the data product and ensuring you meet all organizational policies and requirements, you can initiate an access request by clicking the Request Access button at the top right of the data product detail page. This opens the access request modal, which guides you through three consecutive steps:

1. Consumer Info

   In this step, provide information about the consumer for whom access is being requested. You can create requests for yourself or for other users. Select the consumer from the available options. The consumer type can be:

   • Data Product: A data product defined in the Blindata Catalog
   • User: A user registered within Blindata (defaults to the currently authenticated user)
   • Team: A team defined within Blindata
   • Application: An external application (requires Application Identifier and Display Name)

   You may also specify a service account to which access should be granted.

   Once all required information is entered, click Next to proceed.

   

2. Provider Info

   Here, a table lists all available output ports. Select the ports for which you are requesting access. You can use the top-left checkbox to select all available ports quickly.

   After making your selections, you can:

   • Click Next to proceed to the final step (Properties)
   • Click Save to save the request as a draft
   • Click Submit to submit the request for approval

   

   Info

   If any mandatory custom properties have been set by the MARKETPLACE_ADMIN, you must provide them in the next step before saving or submitting the request.

3. Properties

   In this step, provide all general information and metadata required to process your request. Most fields are auto-completed but can be edited as needed:

   • Name: The name of the access request
   • Identifier: The unique identifier for the request
   • Description: A brief description of the intended usage or other relevant details
   • Start / End Date: The validity period of the request
   • Additional Properties: Any extra information you wish to provide
   • Custom Properties: If defined by your system administrator, these may include intended usage, purpose, or use case. Mandatory custom properties must be provided to submit the request.

   

4. Saving / Submitting the Request

   Once all required information is provided, you can:

   • Save the access request as a draft to edit later
   • Submit the request for approval. A notification will be sent to the responsible providers, and you will need to wait for their decision.

Editing an Access Request Before Submission

When you create an access request but are not yet ready to submit it for approval, you can choose to save it as a draft. Draft requests are not visible to providers and do not trigger any notifications—they are private to you until you decide to submit them.

While your request is in DRAFT status, you have complete flexibility to review and update any of its details. This includes changing the consumer, modifying the list of requested ports, updating the justification or description, and editing any custom or required properties. To make changes, simply navigate to the access request detail page and click the Modify button. This will reopen the access request modal, allowing you to adjust any information as needed.

If you decide that you no longer need the draft request, or if you created it by mistake, you can delete it at any time before submission. To do this, click the Delete button on the access request detail page. Deleting a draft is permanent and cannot be undone.

Important: Once you are satisfied with your draft and click Submit, the request is formally sent for provider review. At this point, the request status changes from DRAFT to PENDING, and the responsible providers are notified. After submission, you can no longer edit or delete the request. If it is denied, you can create a new request with the necessary corrections.

Submitting an Access Request for Approval

To submit an access request for approval, you have two main options:

• From the Access Request Modal: After you have filled in all required fields and completed any necessary edits, click the Submit button at the bottom of the modal. This action will immediately send your request for provider review.
• From the Draft Request Detail Page: If you previously saved your request as a draft, navigate to the request’s detail page. Here, you will find a Submit button that allows you to formally submit the draft for approval.

Once you submit your access request, the following occurs:

• The request status changes from DRAFT to PENDING, indicating that it is now awaiting provider review.
• All users assigned as responsible providers for the target data product will receive notifications (both in-app and, if configured, via email) alerting them to your new request.
• Your request becomes locked for further editing or deletion. You will not be able to make changes unless the provider denies your request, at which point you can create a new one if needed.
• You can monitor the status of your request and see when it is approved, denied, or if further action is required.

Usage Guidelines:

1. Always review data product documentation before requesting access.
2. Provide clear justification for access requests.
3. Follow data usage guidelines.
4. Keep track of your active access.
5. Report any issues or concerns promptly.

Unsubscribing

If you no longer require access and your request has already been approved, you can click the Unsubscribe button to initiate termination. This will notify the provider, who is responsible for handling the unsubscription and revoking your access. After you submit the unsubscription request, the request status will update immediately, but actual access to the ports will only be revoked once the provider completes the port access revocation process.

Understanding the Lifecycle and Statuses

Below is a summary of the main statuses an access request can have, what triggers each status, and what actions are possible at each stage:

Each port within an access request can have its own status, reflecting the current stage of access for that specific port. Refer to the table below for an explanation of each possible port status.

To view more information about a port’s status, click the Access status info icon (when available) next to the status on your access request details page.

Viewing Your Requests

To view and manage all your access requests in the Marketplace, start by clicking the Marketplace tab, which is located at the top right of the data product catalog page. This will take you to the Access Requests list page, where you can see a comprehensive overview of all requests you have submitted, as well as any requests where you are listed as the direct consumer.

On this page, you have several tools to help you find and track your requests:

• Quick Filters: Instantly filter your requests to show only those you have created or where you are listed as the consumer.
• Status Filter: Use the status dropdown to view requests in a specific state, such as only those that are currently pending approval or those that have been approved.
• Advanced Filters: For more granular searching, you can filter requests by additional criteria, including:
  • Provider: See requests associated with a specific provider data product.
  • Consumer Type: Filter by the type of consumer (e.g., data product, user, team or application).
  • Consumer: Search for requests associated with a specific consumer.
  • Validity Period: Narrow down requests based on their requested start and end dates, helping you track active or upcoming access.

Each request entry displays key information, such as the data product name, request status, submission date, and the current stage of the approval or access process. You can click on any request to open its detail page, where you will find a full history of actions, comments, and the status of each individual port included in the request.

Additionally, the Marketplace system will send you notifications for any important updates to your requests. These notifications cover events such as when your request is approved, denied, revoked, or when there is a change in the status of access to specific ports. Notifications are delivered both in-app and, depending on your settings, via email, ensuring you are always informed about the progress and outcome of your access requests.

All Notifications Received by the Consumer

This is a reference list of all notifications sent to the Consumer during the lifecycle of an Access Request: