liveBook · Manning

Relationship-based access control

Relationship-based access control is an authorization technique that makes decisions from defined relationships among principals, resources, groups, and other entities.

How 2 Manning books explain it

Authorization in Action

A relationship permission is an access rule or authorization pattern in which permission depends on an authorization-relevant relationship between entities.

How it is used
Supports fine-grained sharing and delegation in collaborative, multi-tenant systems without replacing broad job roles.
How deep it goes
Explains graph traversal, stable rules, authorization architecture, governance tradeoffs, and Cedar policy patterns.
Examples
Uses shared documents, support tickets, ownership, and managers’ access to their reports’ resources.
What you can do after
Apply it via Cedar policies for ownership and management relationships, alongside attribute-based constraints.

Read how Authorization in Action explains relationship-based access control →

Software Security for Developers

Relationship-based access control, or ReBAC, is an access-control technique that makes authorization decisions from relationships among entities such as users, resources, groups, and projects.

How it is used
Uses connections among users, groups, projects, and resources to make fine-grained authorization decisions.
How deep it goes
Explains entities, relationships, use cases, deployment patterns, and tradeoffs, but stops short of full policy implementation.
Examples
Uses shared documents, team ownership, project access, organizational hierarchies, delegation, and central relationship-store queries.
What you can do after
Evaluate whether relationship-driven authorization fits collaborative, multitenant, hierarchical, or delegated access patterns.

Read how Software Security for Developers explains relationship-based access control →

What to know first

Related concepts

Questions about relationship-based access control

What is relationship-based access control?

Relationship-based access control is an authorization technique that makes decisions from defined relationships among principals, resources, groups, and other entities.

Which Manning books explain relationship-based access control?

Authorization in Action and Software Security for Developers.

What should I know before learning relationship-based access control?

Manning books that teach relationship-based access control usually introduce microservice architecture first.

What is the difference between relationship-based access control and attribute-based access control?

Relationship-based access control is an authorization technique that makes decisions from defined relationships among principals, resources, groups, and other entities. Attribute-based access control is an authorization model that evaluates subject, resource, action, and contextual attributes against policies to make access decisions.

What is relationship-based access control a kind of?

Relationship-based access control is a kind of authorization model. An authorization model is a formal scheme that represents authority and determines whether subjects may perform actions on resources.

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.