Access Control Lists (ACLs)
What You'll Learn
You'll learn how ACLs map users and groups to resources with specific permissions, and when this authorization model works best.
The Core Concept
An Access Control List (ACL) is a straightforward authorization model that attaches a list of permissions directly to each resource. Think of it like a guestlist at the door of an exclusive club—each resource (the club) maintains its own list of who can enter and what they're allowed to do inside.
Each ACL entry typically specifies:
- Who (a user or group identifier)
- What resource (a file, API endpoint, database record)
- Which permissions (read, write, delete, execute, etc.)
For example, a document might have an ACL like:
alice: read, writebob: readeditors-group: read, write, delete
When ACLs Work Well
ACLs shine in scenarios where:
Resource-centric control matters: Each file, document, or object needs its own distinct set of permissions. File systems (like UNIX file permissions) use ACLs extensively.
Simple permission models: When you have straightforward operations (read/write/delete) rather than complex business rules.
Direct ownership: Resources where individual users or small groups "own" specific items—think shared documents or project folders.
Small-to-medium scale: Managing individual ACLs becomes unwieldy with thousands of resources or complex organizational hierarchies.
When ACLs Struggle
ACLs can become problematic when you need to change permissions across many resources at once, or when authorization logic depends on context (time of day, location, request attributes). For complex enterprise scenarios, role-based or attribute-based models often work better.
Key Takeaway: ACLs provide resource-centric authorization by attaching permission lists directly to each protected resource—simple and effective for ownership-based access patterns, but challenging at scale or with complex rules.