What you will be able to do
- Decide whether a data product belongs on the public Snowflake Marketplace, a private listing, or the Internal Marketplace
- List the account, terms and role requirements for becoming a listing provider
- Grant a custom role the privileges it needs to create and own listings
- Create, edit and delete a provider profile, and know when one is required
Key concept
Listing — A listing is the unit a provider offers to consumers. It wraps a data product (a secure share, a Snowflake Native App or a Connected App) with a title, description, terms and an audience, and the audience decides where it can be discovered: the public Snowflake Marketplace, specific named accounts, or the organization's Internal Marketplace.
1.Where listings appear: public Marketplace, private listings and the Internal Marketplace
Every listing has an audience, and the audience decides who can discover it. Underneath, the product is usually a share, the same object described in Outbound shares and sharing models. The listing adds what a bare share lacks: a title and description, legal terms, optional pricing, and a place where consumers can find it. Choosing the audience is the first design decision, because it fixes where the listing is visible and what the provider account has to set up before publishing.
| Listing type | Who sees it | Products it can carry |
|---|---|---|
| Public free | Anyone browsing the Snowflake Marketplace; full product immediately, no charge | Dataset (secure share) or Snowflake Native App |
| Public paid | Anyone browsing the Snowflake Marketplace; consumers are charged for access | Dataset, Snowflake Native App, or Connected App |
| Limited trial | Snowflake Marketplace; limited access immediately, full product on request | Any product the provider later fulfils |
| Private (Specified Consumers) | Only the accounts the provider names | Dataset or Snowflake Native App, free or paid |
The Internal Marketplace is the third audience. It works like the public Marketplace but only accounts in your own organization can see it, and the listings published there are called organizational listings. Providers create them in Provider Studio or through the API, and access is scoped by targeting specific accounts and by role-based access control, so a listing can be visible to one role in one account and hidden from everyone else. Consumers browse it in Snowsight under Catalog » Internal Marketplace, or list what they can see with SHOW AVAILABLE LISTINGS IS_ORGANIZATION = TRUE;.
title: "My title"
description: "One region, two accounts, four roles"
organization_profile: INTERNAL
organization_targets:
access:
- account: "<account_name>"
roles:
- "<role>"
- "<role>"
- account: "<account_name>"
roles:
- "<role>"
- "<role>"
locations:
access_regions:
- name: "PUBLIC.<snowflake_region>"Choose by who the consumer is. If a finance account owns a curated revenue dataset that analysts in eleven sister accounts should find and request, but that must never leave the company, an organizational listing is the right fit. Direct shares to each account would work, but nobody could browse or discover them. A public listing is the wrong tool: the public Marketplace exists for consumers outside your organization, and there is no setting that narrows it to your own accounts. Choose the public Marketplace when you want unknown customers to find you, and a private listing when you already have a relationship with a specific outside account, for example after a trial request.
Checkpoint 1 of 7· Check yourself
A data engineering team owns a curated customer-churn dataset. Analysts in several other accounts in the same Snowflake organization should be able to browse and find it, and only specific roles in those accounts should see it. It must never be offered outside the company. Which approach fits?
Organizational listings in the Internal Marketplace can only be seen by accounts in your own organization. Access can be narrowed by targeting accounts and roles, and consumers can still browse to find the listing. Public Marketplace listings are for outside consumers, and region availability does not limit them to your organization. Direct shares work, but nobody can browse or discover them.
“The Internal Marketplace is similar to the public Snowflake Marketplace, but it is exclusively for your organization.”Source: docs.snowflake.com
Checkpoint 2 of 7· Exam question
A retail company has twelve Snowflake accounts in one organization. The finance account owns a curated revenue dataset that analysts in the other accounts should discover and request through Snowsight, but it must never be visible outside the organization. Which approach BEST fits?
Correct answer: B — Create an organizational listing that surfaces the dataset in the Internal Marketplace for the organization's accounts
- A. A Data Exchange is a private hub for invited members, typically spanning partners; it is not the organization-wide discovery experience and needs membership administration.
- B. An organizational listing appears in the Internal Marketplace so accounts in the same organization can discover and request it, without exposing it to outside customers.
- C. Direct shares work, but they give analysts no catalog to browse and no request workflow, and each share must be created and tracked by hand per account.
- D. A public Marketplace listing is discoverable by all Snowflake customers, and region filters do not restrict it to one organization.
2.Requirements for becoming a listing provider
Becoming a provider is a set of account-level conditions, not a separate signup. To offer listings privately or on the Marketplace, the provider must meet all of the following:
- Use a full Snowflake account. A trial account can share with specified consumers but cannot publish to the Marketplace.
- Not be a reader account.
- Use ACCOUNTADMIN or a role that has been granted provider privileges.
- Accept the legal terms. An organization administrator (ORGADMIN) reviews and accepts the Snowflake Provider and Consumer Terms in Snowsight under Admin » Terms.
The terms requirement has one exception. A provider that only creates free private listings does not need the Provider and Consumer Terms, provided it has accepted the Snowflake Customer-Controlled Data Sharing Functionality Terms instead. If Admin » Terms throws an error when you try to accept, the user profile is usually missing contact details, which an administrator can fill in.
Charging for listings adds two further steps. First, set up a Stripe Express connected account under Admin » Billing » Marketplace billing » Provider billing, which is how payouts arrive. Second, before creating a paid listing for the public Marketplace, contact your Snowflake business development partner, or open a case with Marketplace Operations if you have none. Snowflake requires this for listing approval.
Checkpoint 3 of 7· Check yourself
Which legal-terms setup lets a full Snowflake account publish free private listings to named consumer accounts? The account will never charge for listings or publish on the Snowflake Marketplace.
The Provider and Consumer Terms have one exception: a provider that only creates free private listings can accept the Customer-Controlled Data Sharing Functionality Terms instead. Stripe is needed only for paid listings, and some set of terms is always required.
“You do not need to accept the Snowflake Provider and Consumer Terms if you’re only creating free private listings”Source: docs.snowflake.com
Sources4
3.Roles and privileges for creating and owning listings
Listing work is commonly moved off ACCOUNTADMIN by granting the global CREATE LISTING privilege to a custom role. A role holding it can create listings, and it owns the listings it creates. Once it owns a listing, it can modify and publish it. MODIFY is the other listing privilege, but it is granted on one particular listing, not on the account, so it cannot prepare a role for listings that don't exist yet.
| Task | Required roles and privileges |
|---|---|
| Create a data listing | Global CREATE LISTING; CREATE SHARE; OWNERSHIP (or sufficient grants) on the shared database, schemas and objects |
| Create a Native App listing | Global CREATE LISTING; OWNERSHIP on the application package |
| Modify or configure a listing | OWNERSHIP on the listing, or MODIFY on the listing |
| Publish a listing | OWNERSHIP on the listing; publishing role must own the attached share or application package; an approved provider profile |
Things get complicated when the share and the listing belong to different roles. The role that attaches the data product and publishes the listing has to be the role that owns the share or application package, and ownership of a share cannot be transferred. So if listing_admin owns the listing and data_eng owns the share, grant MODIFY on the listing to data_eng. Granting OWNERSHIP of the share to listing_admin is not possible.
Auto-fulfillment privileges have their own chain of grants. Before ACCOUNTADMIN can create and manage listings that auto-fulfill, ORGADMIN must delegate the auto-fulfillment privileges. For a custom role, ORGADMIN delegates them to ACCOUNTADMIN, which then grants them on to the custom role. That delegation controls replication to remote regions, so it does not give a role the ability to create listings.
Checkpoint 4 of 7· Match them up
A provider account is moving listing work off ACCOUNTADMIN. Match each goal to the grant that achieves it.
Tap a term, then the definition that fits it.
CREATE LISTING is account-level, so it prepares a role for future listings. MODIFY is granted on one existing listing. Share ownership can't be transferred, so a share-owning role gets MODIFY on the listing. Native App listings also require ownership of the application package. Auto-fulfillment privileges go from ORGADMIN to ACCOUNTADMIN to the custom role, and that chain doesn't let anyone create listings.
“grant the MODIFY privilege on the listing to the role that owns the share or application package. You can’t transfer OWNERSHIP of a share.”Source: docs.snowflake.com
Checkpoint 5 of 7· Exam question
A data platform team wants a custom role named listing_admin to create and own listings so that ACCOUNTADMIN no longer has to do this day to day. Which statement, run by ACCOUNTADMIN, is the MOST appropriate way to enable this?
Correct answer: B — GRANT CREATE LISTING ON ACCOUNT TO ROLE listing_admin, so the role can create listings and becomes their owner
- A. MANAGE LISTING AUTO FULFILLMENT only governs cross-region auto-fulfillment settings on listings. It does not grant the right to create or publish a listing.
- B. CREATE LISTING on the account is the global privilege that allows creating listings and provider profiles. By default only ACCOUNTADMIN holds it, and the creating role becomes the listing owner.
- C. MODIFY is a privilege granted on an individual listing, not on the account, and it would not let the role create anything.
- D. IMPORT SHARE lets a role create databases from inbound shares as a consumer. It has nothing to do with creating provider-side listings.
4.Provider profiles: when you need one, and how to manage it
A provider profile is the public identity on your listings: the company name, logo, description and contact details consumers see. You need one for two purposes, either offering paid listings or offering any listing on the public Snowflake Marketplace. Free private listings do not need a profile. Organizational listings in the Internal Marketplace use the built-in INTERNAL organization profile, and custom organization profiles aren't supported. You create a profile once and reuse it, and one account can have several, but each distinct legal entity may have only one.
To create one, open Marketplace » Provider Studio » Profiles, select + Create profile, fill in every field, then Submit for Approval (or Save Draft). Snowflake checks that the terms were accepted and that the profile follows the Provider Policies. Until it is approved, the profile cannot be used for paid or Marketplace listings.
| Field | Visible to consumers | Requirement that commonly causes rejection |
|---|---|---|
| Company icon | Yes | JPG or PNG, up to 2 MB, 256px square recommended; not blurry, cut off or skewed |
| Company name | Yes | Must match your company or a name it publicly does business as |
| Company description | Yes | 2–3 sentences on who you are; must not direct consumers off-platform |
| Consumer contact email | Yes | Business domain; receives access-request notifications; use a group alias |
| Privacy policy link | Yes | Direct link to the policy page, public, not a shortened URL |
| Support link or email | Yes | Business domain, public, not another company's page |
| Business contact email | No | Snowflake contacts you here about your listings |
| Technical contact email | No | Snowflake contacts you here about shared data |
Profiles carry privileges just as listings do. Creating one takes ACCOUNTADMIN or the global CREATE LISTING privilege. Editing or deleting one takes the profile's owner or a role with MODIFY on the profile, and only the owner can grant profile privileges to other roles. To edit, go to Provider Studio » Profiles, open the profile, choose Manage » Update Profile, then Submit for Approval. Most edits are reviewed again before they appear. Changes to the Business Contact and Technical Contact fields are the exception and take effect without approval. Once an edit is approved, it shows on every listing tied to that profile.
Checkpoint 6 of 7· Check yourself
Your full Snowflake account has accepted the required legal terms but has no provider profile. Which of these listings can it publish without creating one?
You need a provider profile for paid listings and for any listing on the public Snowflake Marketplace. A free private listing to named accounts is the only option here that needs neither. A paid listing needs a profile even when it is private, and a free listing needs one once it is on the Marketplace.
“You do not need a provider profile to offer free private listings.”Source: docs.snowflake.com
Checkpoint 7 of 7· Exam question
Your company is preparing to offer data to outside customers. Select TWO of the following situations in which the provider account must first set up a provider profile.(Select 2)
Correct answers: A, D — Offering a paid listing that charges consumers according to a defined pricing plan; Publishing a listing so that it appears on the public Snowflake Marketplace to all customers
- A. Paid listings also require a provider profile, because consumers see the provider's identity and the profile carries the commercial setup.
- B. Organizational listings are shown inside the organization only, so no public provider profile is needed to publish them.
- C. Sharing with a reader account is plain secure data sharing administration and does not involve listings or provider profiles.
- D. Marketplace listings are shown under the provider's name, so a provider profile is required before publishing to the public Marketplace.
- E. A free private listing to a specified consumer does not need Marketplace approval or a provider profile.
Sources
(5)
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.https://docs.snowflake.com/en/user-guide/collaboration/listings/organizational/org-listing-aboutOfficial docs
“The Internal Marketplace is similar to the public Snowflake Marketplace, but it is exclusively for your organization.”
↩︎ Where listings appear: public Marketplace, private listings and the Internal Marketplace“Access can be managed by account targeting and Role-Based Access Control (RBAC)”
↩︎ Where listings appear: public Marketplace, private listings and the Internal Marketplace“Custom organization profiles aren't supported.”
↩︎ Provider profiles: when you need one, and how to manage it - 2.https://docs.snowflake.com/en/user-guide/collaboration/listings/organizational/org-listing-manageOfficial docs
“In the navigation menu, select Catalog » Internal Marketplace.”
↩︎ Where listings appear: public Marketplace, private listings and the Internal Marketplace - 3.
“A listing on the Snowflake Marketplace that gives consumers the full product immediately, at no charge.”
↩︎ Where listings appear: public Marketplace, private listings and the Internal Marketplace“You can’t transfer OWNERSHIP of a share.”
↩︎ Roles and privileges for creating and owning listings“A listing combines a product with a way for consumers to get it.”
↩︎ Key concept“grant the MODIFY privilege on the listing to the role that owns the share or application package”
↩︎ Exam trap 2“grant the MODIFY privilege on the listing to the role that owns the share or application package. You can’t transfer OWNERSHIP of a share.”
↩︎ Checkpoint - 4.
“an organization administrator (ORGADMIN) needs to review and accept the combined Snowflake Provider and Consumer Terms.”
↩︎ Requirements for becoming a listing provider“You do not need to accept the Snowflake Provider and Consumer Terms if you’re only creating free private listings”
↩︎ Requirements for becoming a listing provider“You must not be using a Reader Account.”
↩︎ Requirements for becoming a listing provider“must be the same role that created, and therefore owns, the application package or share.”
↩︎ Roles and privileges for creating and owning listings“If you use a custom role, the ORGADMIN role must first Delegate privileges to set up auto-fulfillment to the ACCOUNTADMIN role”
↩︎ Roles and privileges for creating and owning listings“To offer paid listings or any listings on the Snowflake Marketplace, you must create a provider profile.”
↩︎ Provider profiles: when you need one, and how to manage it“You only need to create a provider profile one time. You can create multiple provider profiles for one account.”
↩︎ Provider profiles: when you need one, and how to manage it“You do not need a provider profile to offer free private listings.”
↩︎ Exam trap 1“You must use a full Snowflake account. Trial accounts can share data with specified consumers, but not on the Snowflake Marketplace.”
↩︎ Prediction“You do not need a provider profile to offer free private listings.”
↩︎ Checkpoint - 5.
“The profile owner (a role with OWNERSHIP of the profile), or a role with the MODIFY privilege on the profile”
↩︎ Provider profiles: when you need one, and how to manage it“Updating the Business Contact and Technical Contact fields in your provider profile does not require approval from Snowflake.”
↩︎ Provider profiles: when you need one, and how to manage it“You may only have one profile per distinct legal entity.”
↩︎ Provider profiles: when you need one, and how to manage it