Skip to main content

🏢 Organizations & Multi-Account Management

As your Snowflake footprint grows, managing multiple Snowflake accounts becomes a necessity for isolating environments, meeting data residency requirements, or managing different business units. Snowflake Organizations provide a centralized way to administer, govern, and monitor all your accounts.


1. What is a Snowflake Organization?​

A Snowflake Organization is a top-level administrative grouping that links all of your company's Snowflake accounts together.

Instead of managing billing, usage, and account provisioning independently for each account, an Organization allows you to centrally:

  • Provision new accounts across different cloud providers (AWS, Azure, GCP) and geographic regions.
  • View billing and usage data aggregated across all accounts.
  • Manage database replication and data sharing between accounts.
  • Centralize security policies and certain parameters.

The ORGADMIN role is not enabled by default for all users. An existing ORGADMIN must use the GRANT ROLE ORGADMIN TO USER <username> command to assign it. If you are a new customer, Snowflake assigns ORGADMIN to the initial user created during the account setup.

3. Creating & Managing Accounts​

With the ORGADMIN role, you can instantly spin up new Snowflake accounts on demand.

Creating an Account via SQL​

You can programmatically create accounts using the CREATE ACCOUNT command. This is highly useful for infrastructure-as-code (IaC) workflows.

USE ROLE ORGADMIN;

CREATE ACCOUNT my_new_prod_account
ADMIN_NAME = 'admin_user'
ADMIN_PASSWORD = 'super_secure_password'
EMAIL = 'admin@mycompany.com'
EDITION = 'ENTERPRISE'
REGION = 'AWS_US_EAST_1';

Account Naming & URLs​

When you create accounts within an Organization, you use the Organization Name and Account Name format to access them.

  • Format: https://<orgname>-<accountname>.snowflakecomputing.com
  • This is much cleaner and easier to remember than the legacy "Account Locator" format.

4. Cross-Account Operations​

Organizations enable powerful features that span across your individual accounts:

Centralized Usage & Billing​

🎭 Interactive Lab: The "Secondary Roles" Trap

If you run the following code as an ORGADMIN, you will receive a privilege error:

USE ROLE ORGADMIN;
SELECT CURRENT_ROLE();

CREATE TABLE TEST_TABLE(
ID NUMBER
);
-- ❌ ERROR: Insufficient privileges to operate on schema

But, if you run this INSERT statement in the same session, it magically succeeds!

INSERT INTO DEMO_DB.RAW.CUSTOMERS (CUSTOMER_ID, NAME, EMAIL, COUNTRY, CREATED_AT) VALUES
(6, 'Testin', 'Testin.johnson@example.com', 'USA', '2025-11-12 08:45:00');
-- ✅ SUCCESS

🤔 Question: Why did the DML (INSERT) succeed when the DDL (CREATE TABLE) failed?

💡 Click here to reveal the answer!

This happens because of Secondary Roles! DML operations (like INSERT and SELECT) can be authorized by any active secondary role in your session (such as SYSADMIN or ACCOUNTADMIN). However, DDL operations (like CREATE) must be authorized by your primary role, which in this case is ORGADMIN.

📖 Dive deeper in our full lab: The Secondary Roles Trap

💡 Pro Tip: The ORGADMIN Role

Keep these three rules in mind regarding the ORGADMIN role:

  1. Not Enabled by Default: Standard users will not see or have access to this role out-of-the-box.
  2. First User Advantage: If you are a brand new customer, Snowflake automatically assigns ORGADMIN to the very first user created during account setup.
  3. Explicit Grants Required: To give others access, an existing ORGADMIN must explicitly run: GRANT ROLE ORGADMIN TO USER <username>;

5. Multi-Account Strategy & Best Practices​

When should you create a new account versus just creating a new database?

  • Use Separate Databases/Schemas when you want to share data easily within the same business unit, and you are fine with administrators having visibility across the environment.
  • Use Separate Accounts for:
    • Environment Isolation: Complete separation of Development, Testing, and Production environments. This prevents accidental data drops or compute resource contention.
    • Data Residency: If a specific dataset must physically reside in the EU, you must create an EU-based Snowflake account for it.
    • Business Unit Isolation: If two subsidiaries or business units need completely separate billing and administration teams.
    • Regulatory Compliance: Strict compliance requirements (like HIPAA or FedRAMP) often dictate complete tenant isolation.

[!IMPORTANT] Establish a strict naming convention for your accounts early on (e.g., ORG-DEV-AWS-USEAST1, ORG-PROD-AZURE-WESTEU). Since an account name cannot be easily changed later without contacting support, getting this right from day one is critical.