Access control is the set of rules that decides who can do what with each asset: see it, preview it, download the original, edit its metadata, share it onward, or delete it. In a DAM, those rules are enforced by the system on every request — not implied by which folder a file happens to sit in.

The reason folder-based permissions fail for asset libraries is that assets belong to many contexts at once. A product image is part of a campaign, a product family, a regional selection, and a press kit simultaneously; copying it into four permission-scoped folders creates four governance problems. Asset-level access control keeps one file with one set of rules, evaluated against who is asking — an employee, an agency partner, or an anonymous portal visitor — and what exactly they are trying to do. The distinction between actions matters: letting everyone browse previews while restricting original downloads to approved users is a common and healthy pattern.

Access control is also what makes wider sharing safe. Portals, share links, and API consumers all pass through the same rule evaluation, so opening the library to guests never means opening all of it. And because rules are enforced centrally, a change takes effect everywhere at once — revoking a group's access doesn't require hunting down every place an asset was exposed.

In freedam, access rules are evaluated per asset and per action — view, preview, download original, share — including for unauthenticated portal guests, who are governed by the same rule engine as logged-in users.

Related terms: Embargo, Audit Trail, Brand Portal