Multi-account and organization management in Snowflake - Step-by-Step Execution

Process Flow - Multi-account and organization management

Create Organization

↓

Add Accounts to Organization

↓

Define Roles and Permissions

↓

Manage Resource Access Across Accounts

↓

Monitor and Audit Activity

↓

End

This flow shows how an organization is created, accounts are added, roles set, resources managed, and activities monitored.

Execution Sample

Snowflake

CREATE ORGANIZATION my_org;
CREATE ACCOUNT my_account1;
ADD ACCOUNT my_account1 TO ORGANIZATION my_org;
GRANT ROLE ORGADMIN TO USER admin_user;
SHOW ORGANIZATION ACCOUNTS;

This code creates an organization, adds an account, assigns an admin role, and lists accounts in the organization.

Process Table

Step	Action	Command Result	State Change
1	Create organization 'my_org'	Organization 'my_org' created	Organization 'my_org' exists with no accounts
2	Create account 'my_account1'	Account 'my_account1' created	Account 'my_account1' exists, not linked
3	Add 'my_account1' to 'my_org'	Account 'my_account1' added to organization 'my_org'	'my_account1' linked to 'my_org'
4	Grant ORGADMIN role to 'admin_user'	Role ORGADMIN granted to user 'admin_user'	'admin_user' can manage organization
5	Show organization accounts	Lists: 'my_account1'	Confirms 'my_account1' is in 'my_org'
6	End	No further actions	Setup complete

💡 All steps executed; organization with one account and admin role configured

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
Organization 'my_org'	None	Exists	Exists	Exists with 'my_account1'	Exists with 'my_account1'	Exists with 'my_account1'	Exists with 'my_account1'
Account 'my_account1'	None	None	Exists	Linked to 'my_org'	Linked to 'my_org'	Linked to 'my_org'	Linked to 'my_org'
User 'admin_user' roles	None	None	None	None	Has ORGADMIN role	Has ORGADMIN role	Has ORGADMIN role

Key Moments - 3 Insights

Why do we need to add accounts to the organization after creating them?

Creating an account alone does not link it to the organization. Step 3 shows adding the account to the organization to manage it centrally.

What does granting the ORGADMIN role to a user do?

Step 4 grants the ORGADMIN role, which allows the user to manage organization-wide settings and accounts, as shown in the variable tracker.

How can we confirm the account is part of the organization?

Step 5 runs 'SHOW ORGANIZATION ACCOUNTS' which lists accounts linked to the organization, confirming the state change.

Visual Quiz - 3 Questions

Look at the execution table, after which step is the account 'my_account1' linked to the organization?

A After Step 2

B After Step 4

C After Step 3

D After Step 5

💡 Hint

Check the 'State Change' column for Step 3 in the execution table.

According to the variable tracker, what roles does 'admin_user' have after Step 4?

A ORGADMIN role

B No roles assigned

C AccountAdmin role

D SYSADMIN role

💡 Hint

Look at the 'User admin_user roles' row after Step 4 in the variable tracker.

If we skipped Step 3, what would the 'SHOW ORGANIZATION ACCOUNTS' command display at Step 5?

A It would list 'my_account1'

B It would list no accounts

C It would show an error

D It would list all accounts in Snowflake

💡 Hint

Refer to the execution table Step 3 and Step 5 state changes.

Concept Snapshot

CREATE ORGANIZATION org_name;  -- creates an organization
CREATE ACCOUNT account_name;  -- creates an account
ADD ACCOUNT account_name TO ORGANIZATION org_name;  -- links account
GRANT ROLE ORGADMIN TO USER user_name;  -- assigns admin role
SHOW ORGANIZATION ACCOUNTS;  -- lists accounts in org
Use these commands to manage multiple accounts centrally.

Full Transcript

This visual execution traces how to manage multiple Snowflake accounts within an organization. First, an organization is created. Then, accounts are created separately and added to the organization to link them. Roles like ORGADMIN are granted to users to allow management of the organization. Finally, commands like SHOW ORGANIZATION ACCOUNTS confirm the setup. Variables track the existence and linkage of organizations, accounts, and user roles step-by-step.

Practice

1. What is the main benefit of using Multi-account management in Snowflake?

easy

A. It groups multiple Snowflake accounts under one organization for easier management.

B. It allows running queries faster by combining accounts.

C. It automatically backs up data across accounts.

D. It merges all accounts into a single database.

Solution

1. Step 1: Understand Multi-account management purpose

   Multi-account management groups Snowflake accounts under one organization to simplify management tasks.

2. Step 2: Identify the main benefit

   This grouping helps manage users, billing, and security more easily across accounts.

3. Final Answer:

   It groups multiple Snowflake accounts under one organization for easier management. -> Option A

4. Quick Check:

   Multi-account management = Group accounts for easier management [OK]

Hint: Think of it as organizing accounts like folders in one place [OK]

Common Mistakes:

• Confusing account grouping with data merging
• Assuming it speeds up queries automatically
• Thinking it backs up data across accounts

2. Which Snowflake SQL command is used to create a new organization for multi-account management?

easy

A. CREATE ORG my_org;

B. CREATE ACCOUNT my_org;

C. CREATE MULTI_ACCOUNT my_org;

D. CREATE ORGANIZATION my_org;

Solution

1. Step 1: Recall the correct syntax for creating an organization

   The correct command to create an organization is CREATE ORGANIZATION <name>;.

2. Step 2: Compare options

   Only CREATE ORGANIZATION my_org; uses the exact syntax CREATE ORGANIZATION my_org;. Others use invalid or non-existent commands.

3. Final Answer:

   CREATE ORGANIZATION my_org; -> Option D

4. Quick Check:

   Organization creation command = CREATE ORGANIZATION [OK]

Hint: Remember: 'ORGANIZATION' keyword creates org, not 'ACCOUNT' [OK]

Common Mistakes:

• Using CREATE ACCOUNT instead of CREATE ORGANIZATION
• Using shorthand commands like CREATE ORG which don't exist
• Confusing multi-account with multi-database commands

3. Given the following commands executed in Snowflake:

CREATE ORGANIZATION org1;
CREATE ACCOUNT acc1 IN ORGANIZATION org1;
CREATE ACCOUNT acc2 IN ORGANIZATION org1;
SHOW ACCOUNTS IN ORGANIZATION org1;

What will the last command display?

medium

A. A list showing acc1 and acc2 accounts under org1.

B. An error because SHOW ACCOUNTS is invalid.

C. Only acc1 account details.

D. An empty list because accounts are not linked automatically.

Solution

1. Step 1: Understand account creation in an organization

   Accounts acc1 and acc2 are created inside organization org1, linking them properly.

2. Step 2: Interpret SHOW ACCOUNTS command

   The command lists all accounts under the specified organization, so it will show both acc1 and acc2.

3. Final Answer:

   A list showing acc1 and acc2 accounts under org1. -> Option A

4. Quick Check:

   SHOW ACCOUNTS IN ORGANIZATION lists all linked accounts [OK]

Hint: SHOW ACCOUNTS lists all accounts in the organization [OK]

Common Mistakes:

• Thinking SHOW ACCOUNTS is invalid syntax
• Assuming only one account shows by default
• Believing accounts are not linked automatically

4. You run this command but get an error:

CREATE ACCOUNT acc3 IN ORGANIZATION org2;

The organization org2 does not exist. How do you fix this?

medium

A. Change the command to CREATE ACCOUNT acc3 WITHOUT ORGANIZATION;

B. Create the organization org2 first using CREATE ORGANIZATION org2;

C. Use CREATE ORGANIZATION acc3; instead of CREATE ACCOUNT;

D. Delete acc3 and recreate it without specifying organization.

Solution

1. Step 1: Identify cause of error

   The error occurs because org2 does not exist, so the account cannot be linked to it.

2. Step 2: Fix by creating the organization first

   Use CREATE ORGANIZATION org2; to create the organization before adding accounts.

3. Final Answer:

   Create the organization org2 first using CREATE ORGANIZATION org2; -> Option B

4. Quick Check:

   Organization must exist before adding accounts [OK]

Hint: Always create organization before adding accounts to it [OK]

Common Mistakes:

• Trying to create account without existing organization
• Using wrong commands like CREATE ORGANIZATION acc3
• Assuming accounts can exist without organizations

5. You want to manage billing for multiple Snowflake accounts centrally. Which approach using multi-account and organization management is best?

hard

A. Use separate organizations for each account to track billing individually.

B. Keep accounts separate and manually combine bills outside Snowflake.

C. Create an organization and add all accounts to it, then enable centralized billing.

D. Merge all accounts into one account to simplify billing.

Solution

1. Step 1: Understand billing management with organizations

   Snowflake allows centralized billing by grouping accounts under one organization.

2. Step 2: Choose the best approach

   Creating an organization and adding accounts to it enables centralized billing and easier management.

3. Step 3: Evaluate other options

   Keeping accounts separate or merging accounts is less efficient or not supported for billing. Separate organizations prevent central billing.

4. Final Answer:

   Create an organization and add all accounts to it, then enable centralized billing. -> Option C

5. Quick Check:

   Central billing = One organization with multiple accounts [OK]

Hint: Group accounts in one organization for centralized billing [OK]

Common Mistakes:

• Trying to merge accounts instead of grouping
• Using separate organizations which block central billing
• Manually combining bills outside Snowflake