Permissions are the controls that determine which assets a user can search, view, edit, and distribute. They are not the same as rights management: permissions govern what a user can do inside the system, while rights govern what may legally be done with an asset. Together they keep the library secure and the experience simple.
Why it matters
Without permissions, every asset is available to everyone, which means confidential or out-of-date material can be viewed and downloaded by anyone, and there is no record of where a licensed asset may be used. With permissions in place, users see only the assets that help them work, which is both safer and less cluttered.
How it shows up in practice
A team first identifies its stakeholder groups, then assigns a small number of administrators, the only people who can edit folder structures, change settings, and grant access. Each admin sets the line between efficiency and security: who can upload, which folders are protected, whether users see the whole library or only their slice. External access is handled two ways: a freelancer gets a scoped upload link to one folder, while a long-term agency partner gets an account with permissions limited to its assets. The most overlooked piece is offboarding, defining what happens to access when someone leaves.
Common mistakes
- Granting too many administrators, multiplying the chance of human error.
- Never defining an offboarding process for departing users.
- Making everything open "to keep things simple," and creating real risk.
- Forgetting to track expiring rights on licensed assets.
Stacks covers the structure in managing DAM permissions.