Building Permissions into Data Modeling
summary
A production permission framework at Meta combines a rule engine that evaluates named rules (with optimization like parallel execution and ordering to run the cheapest decisive rule first), a permission schema that centralizes per-entity permissions and lets rules be reused across policies to avoid duplication, and API integration that enforces checks and enables conditional loading (avoids loading a video player when the viewer lacks play rights). It reports measurable gains in reliability and runtime cost.
AI-written summary · about
chapters (7)
- 0:00Permission modeling basics
- 0:44Why permission framework
- 2:33Permission design challenges
- 6:20Core permission framework
- 9:48Centralized permission schema
- 12:20API enforcement
- 13:43Summary & Q&A
related talks
21mSecuring Backstage Plugins Using the Permissions Framework
09mFlexible Authorization:Storing and Managing Rules in DB
39mUnified permission management between API and client
49mFine Grained Authorisation with Relationship-Based Access Control
51mAuthorization beyond @RolesAllowed
51mPermissions: Centralized or Decentralized? Both!
26mCan It Be Done? Building Fine-Grained Access Control for Back...
41mFine Grained Authorisation with Relationship-Based Access Control