liveBook · Manning

Role-based access control

As explained in Grokking Relational Database Design

Role-based access control is an access-control model in which permissions are assigned to roles and users receive permissions through those roles.

Role-based access control (RBAC) protects database confidentiality by assigning permissions to roles, then assigning users to those roles instead of granting permissions individually. section 7.4

A database team

In a high school database, different roles can control access to student records. In The Sci-Fi Collective database, a standard user can read products and add purchases or reviews, while an analyst can read the relevant tables. section 7.4

How Grokking Relational Database Design covers it

How deep it goes
Works through role creation, permission grants, user assignment, and default-role configuration with SQL examples.
Examples
Uses high-school records and Sci-Fi Collective tables to illustrate standard-user, analyst, and admin permissions.
What it assumes
Requires no stated background; defines access control and contrasts mandatory access control before applying RBAC.
What you can do after
Apply it via SQL by creating roles, granting table permissions, assigning users, and enabling default roles.
How it connects
Connects access control with confidentiality, encryption, mandatory access control, users, roles, and database permissions.

Also explained in

Compare how 16 books explain role-based access control →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Relational Database Design. The section links point to the parts of the book it draws on.