Permissions that know relationships.
A parent sees their child’s records; a doctor sees only their patients — enforced by the platform, not by your code.
Spinning up your private demo
Creating a private demo family…
Real users, real relationships, real policies — created just for you. No login.
Permissions that know relationships.
Why this matters
What you just saw
Access that understands people, not just logins. A parent automatically sees their own child’s records; a doctor sees only their patients — and nobody had to write those checks by hand.
How it works
You describe the relationships (parent→child, doctor→patient) and a policy once — real users in Maravilla auth, real edges in the relations graph. The platform database enforces the policy on every read and write, so a forgotten check can’t leak data.
The bigger picture
Most systems stop at fixed roles — admin, member, viewer. Real life is a social graph. Build a health app where guardians see their kids’ records, a classroom where teachers see their students’ work, a marketplace where agents act for their clients, a family vault, a team wiki with per-project trust — any app where “who can see what” follows relationships, not job titles. Every new feature inherits the graph’s rules automatically.
Why Maravilla
The usual way is hand-written permission checks in every endpoint — the #1 source of data-leak bugs. Maravilla makes relationship-aware permissions a platform primitive, enforced at the data layer.