Create an organizational listing¶
Before you create an organizational listing, make sure you review the prerequisites, known limitations, and considerations.
Prerequisites¶
You have access to the ORGADMIN role (Organization accounts are optional).
Your organization administrator (ORGADMIN) has signed the terms for listings.
Known limitations¶
This feature is not available in government regions.
You must use the API to target specific regions.
Data products supported: Snowflake Native App Framework and shares.
The following features are not supported when using organizational listings:
Custom creation of profiles.
Marketplace analytics.
Reader accounts.
Considerations¶
Before you target an entire organization, check for external tenants. Adjust the target accounts for your data products before adding them to an organizational listing unless you intend to share with external tenants.
Each share can be attached to one listing.
Each Native App can be attached to one or more listings.
For organization changes (such as mergers) with accounts containing organization listings, contact Snowflake Support.
Access control requirements¶
Use the information provided here to determine the specific roles and privileges that you must have to execute organizational listing SQL commands.
CREATE ORGANIZATION LISTING¶
A role used to execute this SQL command must have the following privileges at a minimum:
Privilege |
Object |
Notes |
---|---|---|
CREATE ORGANIZATION LISTING |
ACCOUNT |
To create and alter organizational listings. |
A role used to execute this SQL command must have at least one of the following privileges at a minimum:
Privilege |
Object |
Notes |
---|---|---|
USAGE |
SHARE |
To attach the specified share to a listing. |
USAGE |
APPLICATION |
To attach the specified Snowflake Native App Framework to a listing. |
MANAGE LISTING AUTO FULFILLMENT¶
A role used to execute this SQL command must have the following privileges at a minimum:
Privilege |
Object |
Notes |
---|---|---|
MANAGE LISTING AUTO FULFILLMENT |
ACCOUNT |
To configure the auto-fulfillment settings. |
Create an organizational listing¶
Create an organizational listing.
Sign in to Snowsight.
Select Data Products » Provider Studio in the left-side navigation menu.
Click + Listing » Internal Marketplace.
Click + Data Product.
In the + Data Product dialog, click + Select.
Navigate to a data product such as a table, a view or other data product.
Alternatively, search for and choose a data product to share.
Select Done when complete.
Select Save.
Specify who can access the listing (the target accounts, roles, and regions).
Click + Access Control. The Access and discovery dialog displays.
In the Grant access section, enter values for the following:
Field
Description
Who can access this data product?
Select one of:
Entire organization Anyone in the organization can access the listing.
Selected accounts and roles Only selected accounts and roles can access.
No accounts or roles are pre-approved (Default) Data product will only be available by request.
Accounts
If Select accounts and roles is selected, select one or more accounts.
Click + Add another account to add second and subsequent accounts.
Selected user roles
If Selected roles is selected, enter one or more roles to grant access.
In the Allow discovery section, enter values for the following:
Field
Description
Who else can discover the listing and request access?
Select one of:
Entire organization (Default) Anyone in the organization can discover listing and request access.
Selected accounts and roles Only selected accounts and roles can discover listing and request access.
Not discoverable by users without access Only users with access can discover this listing.
Accounts
If Select accounts and roles is selected, select one or more accounts.
Click + Add another account to add second and subsequent accounts.
Selected user roles
If Selected roles is selected, enter one or more roles to grant access.
In the Request approval section, enter the email address of the request approver or link to the internal ticketing system.
Provide a title and Uniform Listing Locator (ULL).
Changing a listings title is optional but recommended. See Uniform Listing Locator for more information.
Select Untitled Listing.
For Listing title, enter a descriptive title for your data product.
Select Save or Cancel.
Complete the listing.
Enter addition information about listing page to guide consumers, such as description, data dictionary, usage examples and more.
Note that Support Contact is required
Click Publish to make the listing available in the Internal Marketplace. If you exit without publishing, the listing is saved as a draft, ready for review or the addition of descriptive metadata.
Create an organizational listing from the share with the required attributes included in YAML (entered in $$ delimiters).
This part of the manifest yaml specifies the accounts that will be able to use the organizational listing:
organization_targets:
access:
This example creates a listing using the required settings in the manifest YAML. It targets one role in one account in one region and includes support and approver contacts:
Note
support_contact
is required.
approver_contact
is required if a discovery
target is provided.
USE ROLE <organizational_listing_role>;
CREATE ORGANIZATION LISTING <organizational_listing_name>
SHARE <share_name> AS
$$
title: "My title"
description: "One region, all accounts"
organization_profile: "INTERNAL"
organization_targets:
discovery:
- account: "<account_name>"
roles:
- "<role>"
access:
- account: "<account_name>"
roles:
- "<role>"
support_contact: "support@somedomain.com"
approver_contact: "approver@somedomain.com"
locations:
access_regions:
- name: "PUBLIC.<snowflake_region>"
$$;
For additional examples see Set who can discover and access an organizational listing.