Access for Snowflakes
Access in Snowflake is controlled by role-based access control. Privileges on objects are granted to roles, roles are granted to users and to other roles, forming a hierarchy. System roles such as ACCOUNTADMIN, SYSADMIN and SECURITYADMIN have defined duties, and features like network policies and masking policies add further protection.
Stage: Architecture · Part of the Snowflake roadmap · Last reviewed 19 November 2026
What to learn in Access
- Grant privileges on databases, schemas and tables to custom roles
- Build a role hierarchy and explain how privileges are inherited
- Know the purpose of ACCOUNTADMIN, SECURITYADMIN, SYSADMIN and PUBLIC
- Apply a dynamic masking policy to hide a sensitive column
- Enable multi-factor authentication and network policies for an account
Access interview questions
Why should ACCOUNTADMIN be used sparingly?
It sits at the top of the role hierarchy and controls billing, security and all objects, so mistakes or a compromised session are very costly. Day-to-day work should use narrower roles, with ACCOUNTADMIN kept for rare account-level tasks and protected by MFA.
How does a role hierarchy work in Snowflake?
Roles can be granted to other roles, and the parent role inherits the child's privileges. Granting an analyst role to a manager role gives the manager everything the analyst can do. Users activate one primary role at a time plus any secondary roles.
Where Access fits in the Snowflake roadmap
Access belongs to the Architecture stage (beginner level), which takes about 20 hours. How Snowflake works.
Other units in this stage
Back to the full Snowflake roadmap