Reader Account Data Sharing (Provider-Managed Sharing)
Reader Account Data Sharing (also called Provider-Managed Sharing) is a Snowflake feature that allows a data provider to share data with consumers who do not have a Snowflake account or where the provider wants full control over the consumer environment. It eliminates the need for the consumer to create and manage their own Snowflake account.
✅ What is Reader Account Data Sharing?
-
Definition: A Reader Account is a Snowflake account created and managed by the provider. It is used by the consumer to access shared data. This is part of Secure Data Sharing in Snowflake.
- Unlike external sharing (which requires the consumer to have their own account), Reader accounts are owned and billed by the provider.
- Consumers cannot create their own databases, cannot purchase credits, or manage account-level resources.
- They can query data, create views, and run analytics on shared datasets within the reader account.
✅ Why Use Reader Accounts?
-
Consumers don’t have Snowflake If your customer/partner doesn't have a Snowflake account, you can still share data securely.
-
Full control by provider Provider controls who can access, what resources they get, and how billing is handled.
-
Lower operational overhead for consumers Consumers do not need to worry about account setup, credit management, or security compliance.
-
Quick onboarding Create a reader account in minutes without requiring legal or technical setup on the consumer side.
✅ Key Characteristics
| Aspect | Reader Account |
|---|---|
| Managed By | Provider |
| Billing | Provider pays for storage and compute |
| Consumer | Gets read access, can run queries |
| Allowed Operations | Query shared data, create views, use Snowflake features (except DDL beyond objects in their schema) |
| Not Allowed | Purchasing credits, full admin control |
✅ Use Cases
- B2B Data Sharing: SaaS provider wants to share analytics data with clients who don’t use Snowflake.
- External Reporting: Company shares financial dashboards with partners in a controlled environment.
- Vendor collaboration: Pharmaceutical company shares drug trial results with research partners.
✅ How to Achieve Reader Account Sharing?
Step 1: Enable Data Sharing in Provider Account
Ensure your role is ACCOUNTADMIN.
USE ROLE ACCOUNTADMIN;
Step 2: Create a Share and Grant Access
Create a database and share objects:
-- Create database & schema
CREATE OR REPLACE DATABASE shared_data_db;
CREATE OR REPLACE SCHEMA shared_schema;
-- Create table
CREATE OR REPLACE TABLE shared_schema.sales_data (
order_id STRING,
amount NUMBER,
order_date DATE
);
-- Insert sample data
INSERT INTO shared_schema.sales_data VALUES
('O001', 500, '2025-08-01'),
('O002', 1200, '2025-08-05');
-- Create share
CREATE OR REPLACE SHARE sales_data_share;
-- Grant privileges
GRANT USAGE ON DATABASE shared_data_db TO SHARE sales_data_share;
GRANT USAGE ON SCHEMA shared_schema TO SHARE sales_data_share;
GRANT SELECT ON TABLE shared_schema.sales_data TO SHARE sales_data_share;
Step 3: Create Reader Account
Create the reader account from provider:
CREATE MANAGED ACCOUNT reader_customer_1
ADMIN_NAME = 'reader_admin'
ADMIN_PASSWORD = 'StrongPassword@123'
TYPE = READER
COMMENT = 'Reader account for Customer 1';
- ✅ This creates a Snowflake account fully managed by you.
Step 4: Add Reader Account to Share
Get the account locator for the reader account, then:
ALTER SHARE sales_data_share ADD ACCOUNT = <READER_ACCOUNT_LOCATOR>;
Step 5: Consumer Access
The reader account admin logs in (with credentials you provide), then runs:
-- Create database from share
CREATE DATABASE shared_data_db FROM SHARE <PROVIDER_ORG>.<sales_data_share>;
- ✅ Now they can query shared data without owning an independent Snowflake subscription.
✅ Restrictions
- Reader accounts cannot share data further.
- Provider pays for storage and compute used in the reader account.
- Reader account cannot be converted into a full enterprise account.
- Security & Compliance: Reader accounts inherit provider’s edition & compliance level (e.g., Business Critical).
✅ Best Practices
- Use row access policies for fine-grained security.
- Monitor usage in reader accounts (you pay for compute).
- Restrict reader account role privileges to avoid misuse.
- Consider data masking if PII data is shared.