liveBook · Manning

Role hierarchy

A role hierarchy is an ordering of roles that establishes relative authority or precedence, and may determine which permissions or instructions take priority.

How 2 Manning books explain it

Snowflake Data Engineering

A role hierarchy is an access-control structure in which roles are granted to other roles so higher-level roles inherit lower-level privileges.

How it is used
Deploys centralized privilege management for Snowflake data pipelines and governance.
How deep it goes
Explains inheritance, role separation, managed schemas, future grants, and executable bakery configuration, while deferring broader policy internals.
Examples
Uses bakery database roles BAKERY_FULL, BAKERY_READ, DATA_ENGINEER, and DATA_ANALYST across RAW and RPT schemas.
What you can do after
Build it from scratch with Snowflake SQL by creating roles, assigning privileges, establishing inheritance, and testing permitted queries.

Read how Snowflake Data Engineering explains role hierarchy →

Authorization in Action

A role hierarchy is an authorization structure in which roles can inherit permissions from other roles to represent levels of responsibility.

How it is used
Structures RBAC permissions around progressive organizational responsibility and simplifies access changes when people change roles.
How deep it goes
Explains inherited-permission evaluation and separation-of-duty interactions, but stops short of dynamic context conditions.
Examples
Uses engineer and senior-engineer roles to demonstrate inherited code-approval and directly granted production-deployment permissions.
What you can do after
Evaluate authorization decisions by tracing assigned roles, inherited roles, and their combined permissions.

Read how Authorization in Action explains role hierarchy →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.