Why Role hierarchy in Snowflake? - Purpose & Use Cases

The Big Idea

What if you could control who sees what in your data with just a few role assignments instead of endless permission lists?

The Scenario

Imagine you manage access for a team by writing down who can do what on paper or in a simple list. Every time someone new joins or changes roles, you have to update each list manually for every system resource.

The Problem

This manual way is slow and confusing. You might forget to update a list, give someone too many permissions, or waste hours fixing mistakes. It's like juggling many keys for many doors instead of having a master key.

The Solution

Role hierarchy in Snowflake lets you organize permissions in layers. You create roles that inherit permissions from other roles, so managing access becomes simple and less error-prone. Change one role, and all related roles update automatically.

Before vs After

✗ Before

GRANT SELECT ON TABLE sales TO USER jane;
GRANT INSERT ON TABLE sales TO USER john;

✓ After

CREATE ROLE analyst;
GRANT SELECT ON TABLE sales TO ROLE analyst;
GRANT ROLE analyst TO USER jane;

What It Enables

It enables easy, secure, and scalable access control that grows with your team and data.

Real Life Example

A company uses role hierarchy to give all analysts read access to sales data, while managers get extra rights to update reports, all managed by assigning roles instead of individual permissions.

Key Takeaways

Manual permission management is slow and risky.

Role hierarchy organizes access in layers for easier control.

Changes in roles automatically update permissions for all users assigned.

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