Most access models are built around current teams, applications and structures. They work until the organisation changes, and then exceptions accumulate.
Durable access is designed around roles and intent rather than individuals and one-off requests.
Access designed for today becomes the exception list of tomorrow.
What this means in practice
- Model access around roles and responsibilities, not named users.
- Build review and revocation into the design, not as an afterthought.
- Assume change, and make the model easy to adjust safely.



