Account Management and Data Governance · Topic 1 of 9
Organizations and the Organization Account
Learn what a Snowflake organization gives you, how it is named, account types, the organization account and GLOBALORGADMIN, and available regions.
- 5 min
- An organization links accounts across regions and clouds and enables central usage views, replication, failover and cross-region sharing.
- The organization account: one per organization, Enterprise or higher, cannot be converted,
GLOBALORGADMIN, premiumORGANIZATION_USAGEviews, extra cost. - Organization names: letters and digits, start with a letter; changed only through Snowflake Support.
What it is
A Snowflake organization is the container that links all the accounts a company owns, across regions and cloud platforms. It gives administrators one place to see, create and manage accounts, to watch usage across them, and to use features that need accounts to know each other: replication and failover, and Secure Data Sharing across regions and clouds.
An administrator is expected to know what an organization is for, who manages it, what it costs, and how it is named.
How it works
Benefits and costs
Benefits
- A central view of all accounts and their usage through the
ORGANIZATION_USAGEschema. - Self-service account creation by an organization administrator, instead of a request to Snowflake.
- Replication, failover and sharing between accounts in the same organization, including across clouds.
- Consistent naming: every account is reached as
orgname-account_name.
Costs and trade-offs
- Every account is a separate set of compute and storage; there is no pooled warehouse, so more accounts mean more administration.
- Cross-region and cross-cloud replication and sharing incur data transfer and storage charges.
- The organization account and its premium usage views are populated with data when it is created, which incurs additional cost.
- An organization has an account limit. By default it can hold at most 25 accounts, and Snowflake Support can raise the limit.
If a scenario needs data in several regions or clouds, or needs failover between accounts, an organization is the prerequisite. If it needs only more virtual warehouses, one account is enough.
Organizational tasks
An organization administrator can:
- create accounts (Snowsight: Admin, then Accounts, then + Account, or
CREATE ACCOUNT), - view the list of accounts (
SHOW ACCOUNTSor Snowsight), - rename accounts and manage their old URLs,
- view or change an account's edition,
- drop accounts,
- monitor usage across accounts in
ORGANIZATION_USAGE.
Two roles matter. ORGADMIN is the role used in an ORGADMIN-enabled account. The documentation says that the GLOBALORGADMIN role in the organization account is the role to use for all organization-level tasks, and that ORGADMIN in a regular account is being phased out, with Snowflake notifying customers at least three months before. GLOBALORGADMIN can grant these account-level privileges to other roles so that other users can do organization tasks: APPLY TAG, MANAGE ACCOUNTS, MANAGE LISTING AUTO FULFILLMENT, MANAGE ORGANIZATION CONTACTS, MANAGE ORGANIZATION TERMS and PURCHASE DATA EXCHANGE LISTING.
Create and name an organization
Customers do not run a command to create an organization. A self-service sign up gets an organization with a system-generated name when the first account is created. Accounts set up with Snowflake staff get an organization with a custom name. More accounts are added afterward.
Naming rules for the organization name:
- letters and digits only, starting with a letter,
- no underscores or other delimiters,
- changing it requires Snowflake Support and changes every account URL, so review it before you build identifiers on it.
Any role can see the current name with CURRENT_ORGANIZATION_NAME().
Types of accounts in an organization
| Type | What it is |
|---|---|
| Regular account | A normal Snowflake account that holds data and workloads; named orgname-account_name |
| ORGADMIN-enabled account | A regular account where the ORGADMIN role has been enabled; it can create the organization account |
| Organization account | One per organization; Enterprise Edition or higher; uses GLOBALORGADMIN and holds premium ORGANIZATION_USAGE views |
The organization account is special:
- There is only one per organization.
- You cannot convert an existing account into it. You create it with
CREATE ORGANIZATION ACCOUNTfrom an ORGADMIN-enabled account. - It has no custom account locator.
- Its
ORGANIZATION_USAGEschema has premium views that regular accounts do not have, for exampleTAG_REFERENCESacross all accounts instead of one.
Regions available to an organization
You can create an account only in a region that is enabled for your organization. SHOW REGIONS lists the regions you can use, with the region ID (for example aws_us_east_2) and region group. To use another region, contact Snowflake Support.
Commercial multi-tenant regions share the PUBLIC region group. Each government region has its own region group, and each Virtual Private Snowflake deployment is in a VPS-specific group, and you give the REGION_GROUP when you create an account in a different group. Replication, failover and sharing work only inside a region group.
Common mistakes
Trying to convert an account into the organization account. It must be created new.
Believing the customer creates the organization. It is created for you when the first account is created; only a name change goes through Support.
Choosing a region that is not enabled for the organization. CREATE ACCOUNT fails; check SHOW REGIONS first.
Planning cross-region features without checking the region group. Accounts in different groups, such as a government region and a commercial one, cannot simply replicate between each other.
Using ORGADMIN as the long-term organization role. The documentation names GLOBALORGADMIN in the organization account for organization-level tasks.
What to remember for the exam
- An organization links accounts across regions and clouds and enables central usage views, replication, failover and cross-region sharing.
- The organization account: one per organization, Enterprise or higher, cannot be converted,
GLOBALORGADMIN, premiumORGANIZATION_USAGEviews, extra cost. - Organization names: letters and digits, start with a letter; changed only through Snowflake Support.
- New accounts can only go in regions enabled for the organization;
SHOW REGIONSlists them. - Default account limit is 25 accounts, and Support can raise it.
Check yourself
Can an existing production account be turned into the organization account?
No; create a new one with
CREATE ORGANIZATION ACCOUNTfrom an ORGADMIN-enabled account.Which role does the documentation name for organization-level tasks in the organization account?
GLOBALORGADMIN.Who changes the name of an organization?
Snowflake Support; it cannot be changed with SQL, and it changes all account URLs.
Topic 1 of 9 in Account Management and Data Governance
Test yourself on Account Management and Data Governance
The full Snowflake ADA-C02 question bank has 814 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.