Review products, cart contents, and request status

Products present assets in business terms. Review descriptions, scope, and accountability before online requests. Approved data is delivered offline by responsible teams.

Review product details

From Marketplace > Data Supermarket, verify:

• Name, definition, scenarios.
• Folder, owner, contacts.
• Included assets, refresh frequency, quality information.
• Security class, restrictions, supporting materials.
• Request availability and any browsing prerequisite.

Visibility does not guarantee column access or approval.

Request now

For one product, enter purpose, scope, duration, users, delivery method, and supplementary information. Verify products and applicant information and place delivery needs in usable fields.

Combine through the cart

1. Add products.
2. Remove unnecessary ones and verify versions, scope, and security.
3. Select Request Use and describe shared and product-specific purposes.
4. Confirm the submitted record retains every product.

The cart combines requests, not data, and does not trigger delivery.

Submit text requirements

Describe goals, scope, time grain, duration, contact, and delivery format. Do not expose unapproved sensitive data. The platform records the request; the organization decides whether to build a product.

Approval and offline delivery

Platform states record submission, approval, rejection, or withdrawal. Workflows may include all-participant/any-participant approval, branches, and custom forms.

After approval:

1. Retain request number, approved scope, and validity.
2. Agree delivery with IT/provider.
3. Accept accounts/files/APIs against the approved use.
4. Link delivery evidence to the request number.

Approval does not mean delivered. Keep offline accounts/files out of public product pages.