Digital asset management
Decide who can do what, at every level
Access is set in two places. A file or a collection carries an access level, which decides who can see it at all. A person carries a role, which decides what they can do with the things they can see — and each permission in that role can be narrowed further, to particular access levels or to that person's own content.
Permissions matrix
Library · Global communications
Scroll sideways for all four roles
| Permission | Viewer | Contributor | Editor | Manager |
|---|---|---|---|---|
| View assets | Held, unrestricted | Held, unrestricted | Held, unrestricted | Held, unrestricted |
| View collections | Held, unrestricted | Held, unrestricted | Held, unrestricted | Held, unrestricted |
| Download assets | Not held | Held, unrestricted | Held, unrestricted | Held, unrestricted |
| Upload assets | Not held | Held, unrestricted | Held, unrestricted | Held, unrestricted |
| Edit assets | Not held | Held, but only for their own content | Held, unrestricted | Held, unrestricted |
| Delete assets | Not held | Held, but only for their own content | Held, unrestricted | Held, unrestricted |
“Own” is a permission narrowed to that person’s own content. Any permission can also be limited to particular access levels rather than the whole library.
Illustrative example
Access levels on files and collections
Set on the thing itself, so it holds wherever that thing turns up — in a search, in a workspace, in somebody else's collection.
01
Private
You, and anyone you add by name. The default for anything still being worked on.
02
Library
Everyone who holds a role in that library, at whatever their role permits them to do.
03
Public
Anyone with the link, whether or not they have an account. Deliberately the loudest of the three to choose.
04
Whatever else you need
A level for one region, one partner, one board. Add as many as your organisation actually uses and set them the same way.
Library roles
Roles that match your organisation, not a template
Every permission is a switch: view assets, view collections, download, upload, edit, delete. A role is whichever switches you turn on, and you build as many roles as the work needs.
- Build a role from any combination of permissions
- Narrow any permission to particular access levels, or to a person’s own content
- Roles are set per library, so one person can be a manager in one and a viewer in the next
- Change what a role allows, and everyone holding it changes with it
More in the platform
Libraries and folders
Run as many libraries as you have teams, offices or regions. Each gets its own drive, its own folders and its own people.
Read more
Upload and file-drop
Uploads that resume when a browser dies, and file-drop links that let someone outside your organisation upload to a specific library, workspace or collection.
Read more
Search and filters
Search across one or all your libraries. Find files using standard and custom filters. Use facial recognition to find pictures of people.
Read more
Workspaces
A collaborative space for your projects. Invite individuals or groups. Assign specific permissions — view, edit or comment. You decide.
Read more
Sharing files
Send files using private expiring links. Set download limits, resize files and add custom watermarks and information to protect your content.
Read more
Admin and reporting
Storage, users, activity, uploads and downloads on one easy-to-read dashboard, and a record of who did what with each file.
Read more
API and integrations
We migrate your existing library and connect the platform to what you already run. A REST API lets you build your own portal on top of it.
Read more
Next step
We’d love to explain more…
Still got questions? Curious to see LightRocket in action? Want to know more about pricing?
We’re always happy to show off our system and, yes, we’ll even help out with discounts and pricing.