Role-based access control (RBAC) is a permission model where access rights attach to named roles — viewer, editor, admin — and people inherit those rights by being assigned a role. You grant access once to the role, not fifty times to fifty people.
In plain English
The alternative to RBAC is granting permissions person by person, which works fine until roughly the tenth person. After that, nobody can answer the question "who can delete assets from the campaign library?" without opening fifty individual permission screens, and access granted to someone in a hurry three years ago is still quietly in place.
Under RBAC, that question has one answer: whichever roles include the delete right. Onboarding becomes "assign the editor role," and offboarding becomes "remove the role." The permission logic lives in one place, which is precisely what makes it auditable — a point that matters when an audit trail has to prove who was allowed to do what, not just who did it.
Roles are commonly scoped rather than global. A person can be an editor inside one collection and a viewer everywhere else — Bynder's permissioned collections work this way, which is how a 40-market organization keeps regional teams out of each other's assets without maintaining a separate library per market.
Two different things called "role-based"
This is worth pinning down, because DAM vendors use the phrase in two unrelated senses and both appear on pricing pages.
- Role-based access control answers what a role is permitted to do. Can an editor delete? Can a viewer download the full-resolution master, or only a watermarked preview?
- Role-based licensing answers what a role costs. Daminion prices viewer seats below editor seats, so a team of mostly viewers with a handful of editors pays meaningfully less than it would under flat per-seat pricing.
These are independent. A tool can price by role while offering only coarse permissions, or offer deep permission granularity while charging every seat the same. Filecamp goes further in the other direction still: it charges nothing per seat at all — we created 60 test accounts on its cheapest plan without restriction — so its permission model is folder-based rather than a lever on cost.
Why it matters in a DAM
RBAC is the mechanism that keeps a permission model comprehensible as an organization grows, and it is the thing a compliance review actually inspects. But because "role-based" also describes a pricing structure, a vendor can honestly claim it while meaning something that has no bearing on security at all.
Buyer’s test: when a vendor says "role-based," ask which sense they mean, then ask for the list of rights each built-in role carries and whether you can create a custom role. If roles are fixed and you can't scope one to a single collection, you'll end up back at per-person exceptions — which is the problem RBAC exists to solve.
Related terms
See it in action
Our best DAM software for granular permissions ranking tests how far each tool's roles can actually be scoped, and stress-tests the "unlimited users" claims that make role-based licensing moot.