Role hierarchy in Snowflake - Commands & Configuration

Introduction

Managing access in Snowflake can be complex. Role hierarchy helps by organizing roles so that permissions flow from higher roles to lower roles automatically.

When you want to give a group of users access to multiple resources without assigning permissions individually.

When you need to create a clear structure of who can do what in your Snowflake account.

When you want to simplify permission management by grouping related permissions under roles.

When you want to delegate administration tasks by assigning roles with specific privileges.

When you want to ensure security by controlling access levels through role inheritance.

Commands

Create a new role named 'analyst' to group permissions for data analysis tasks.

Terminal

CREATE ROLE analyst;

Expected Output

Statement executed successfully.

Create a higher-level role 'senior_analyst' that will inherit permissions from 'analyst'.

Terminal

CREATE ROLE senior_analyst;

Expected Output

Statement executed successfully.

Make 'analyst' a child role of 'senior_analyst' so 'senior_analyst' inherits all 'analyst' permissions.

Terminal

GRANT ROLE analyst TO ROLE senior_analyst;

Expected Output

Grant succeeded.

Give 'analyst' role permission to read data from the 'sales_db' database.

Terminal

GRANT SELECT ON DATABASE sales_db TO ROLE analyst;

Expected Output

Grant succeeded.

Check all permissions and inherited roles assigned to 'senior_analyst'.

Terminal

SHOW GRANTS TO ROLE senior_analyst;

Expected Output

grantee_name | granted_role | privilege | granted_on | name

senior_analyst | analyst | ROLE | ROLE | analyst

senior_analyst | SELECT | DATABASE | sales_db

Key Concept

If you remember nothing else, remember: roles can inherit permissions from other roles, making permission management simpler and more organized.

Common Mistakes

Granting privileges directly to users instead of roles.

This makes permission management complex and error-prone as you must update each user individually.

Always grant privileges to roles and assign roles to users.

Not granting child roles to parent roles to create the hierarchy.

Without this, roles do not inherit permissions, defeating the purpose of role hierarchy.

Use 'GRANT ROLE child_role TO ROLE parent_role' to establish inheritance.

Assuming role inheritance is bidirectional.

Inheritance flows only from child to parent; parent role gets child's permissions, not the other way.

Grant child roles to parent roles explicitly to set correct inheritance direction.

Summary

Create roles to group permissions logically.

Use 'GRANT ROLE child_role TO ROLE parent_role' to build role hierarchy.

Assign privileges to child roles so parent roles inherit them automatically.

Practice

1. What does role hierarchy in Snowflake allow you to do?

easy

A. Store data in different regions automatically

B. Create multiple users with the same password

C. Let roles inherit permissions from other roles

D. Schedule queries to run at specific times

Solution

1. Step 1: Understand role hierarchy concept

   Role hierarchy means roles can inherit permissions from other roles, simplifying access management.

2. Step 2: Identify correct description

   Only Let roles inherit permissions from other roles describes this inheritance feature correctly.

3. Final Answer:

   Let roles inherit permissions from other roles -> Option C

4. Quick Check:

   Role hierarchy = permission inheritance [OK]

Hint: Role hierarchy means roles inherit permissions [OK]

Common Mistakes:

• Confusing role hierarchy with user password management
• Thinking role hierarchy controls data storage
• Mixing role hierarchy with query scheduling

2. Which of the following is the correct syntax to grant a role to another role in Snowflake?

easy

A. GRANT ROLE parent_role TO ROLE child_role;

B. GRANT ROLE TO ROLE parent_role child_role;

C. GRANT ROLE child_role TO ROLE parent_role;

D. GRANT ROLE parent_role child_role TO ROLE;

Solution

1. Step 1: Recall Snowflake grant syntax

   To make one role inherit another, you grant the parent role to the child role using: GRANT ROLE parent_role TO ROLE child_role;

2. Step 2: Match syntax to options

   GRANT ROLE parent_role TO ROLE child_role; matches the correct syntax exactly.

3. Final Answer:

   GRANT ROLE parent_role TO ROLE child_role; -> Option A

4. Quick Check:

   Grant parent to child = correct syntax [OK]

Hint: Grant parent role TO child role syntax [OK]

Common Mistakes:

• Reversing parent and child roles in the grant statement
• Incorrect order of keywords in the command
• Missing 'TO ROLE' keyword

3. Given the following role hierarchy:
GRANT ROLE analyst TO ROLE senior_analyst;
GRANT ROLE senior_analyst TO ROLE manager;
If a user is assigned the role manager, which roles' permissions does the user have?

medium

A. Manager and senior_analyst only

B. Manager, senior_analyst, and analyst

C. Only manager

D. Only analyst

Solution

1. Step 1: Trace role inheritance

   Manager role inherits senior_analyst, which inherits analyst. So manager includes all permissions from senior_analyst and analyst.

2. Step 2: Determine user permissions

   User with manager role has permissions from manager, senior_analyst, and analyst roles.

3. Final Answer:

   Manager, senior_analyst, and analyst -> Option B

4. Quick Check:

   Role inheritance includes all ancestor roles [OK]

Hint: User gets all inherited roles' permissions [OK]

Common Mistakes:

• Assuming user only has direct role permissions
• Ignoring transitive inheritance in role hierarchy
• Confusing child and parent roles

4. You run this command:
GRANT ROLE analyst TO senior_analyst;
What is wrong with this command?

medium

A. Cannot grant a role to another role

B. Role names must be in quotes

C. The order of roles is reversed

D. Missing 'ROLE' keyword before 'senior_analyst'

Solution

1. Step 1: Check syntax for granting roles

   The correct syntax requires 'TO ROLE' before the role receiving the grant.

2. Step 2: Identify missing keyword

   The command misses 'ROLE' keyword before 'senior_analyst'. It should be: GRANT ROLE analyst TO ROLE senior_analyst;

3. Final Answer:

   Missing 'ROLE' keyword before 'senior_analyst' -> Option D

4. Quick Check:

   Grant syntax requires 'TO ROLE' [OK]

Hint: Always include 'TO ROLE' keyword in grant statements [OK]

Common Mistakes:

• Omitting 'ROLE' keyword after TO
• Thinking roles cannot be granted to roles
• Using quotes unnecessarily around role names

5. You want to create a role hierarchy where intern inherits from analyst, and analyst inherits from manager. Which sequence of commands correctly sets this up?

hard

A. GRANT ROLE manager TO ROLE analyst; GRANT ROLE analyst TO ROLE intern;

B. GRANT ROLE analyst TO ROLE intern; GRANT ROLE manager TO ROLE analyst;

C. GRANT ROLE manager TO ROLE analyst; GRANT ROLE intern TO ROLE analyst;

D. GRANT ROLE intern TO ROLE analyst; GRANT ROLE analyst TO ROLE manager;

Solution

1. Step 1: Understand inheritance direction

   Child role inherits from parent role by granting parent role TO child role.

2. Step 2: Apply to given roles

   Intern inherits analyst: GRANT ROLE analyst TO ROLE intern;
   Analyst inherits manager: GRANT ROLE manager TO ROLE analyst;

3. Step 3: Match sequence to options

   GRANT ROLE manager TO ROLE analyst; GRANT ROLE analyst TO ROLE intern; matches the correct order and syntax.

4. Final Answer:

   GRANT ROLE manager TO ROLE analyst; GRANT ROLE analyst TO ROLE intern; -> Option A

5. Quick Check:

   Grant parent TO child for inheritance [OK]

Hint: Grant parent role TO child role to inherit [OK]

Common Mistakes:

• Reversing parent and child roles in grants
• Granting child TO parent instead of parent TO child
• Mixing order of commands