These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Digital Asset Management
- Who it's for
- Content operations
Content operations
A content operations team may handle many requests at different points of production. The content item is the working unit: it has a project, owner, due date and state. Production tasks identify the action and person responsible for a particular step. The Business Overview helps the team see the library's status mix and rights that are nearing their end date before assigning the next release.
How Digital Asset Management is set up for you
Intake and ownership
The Content Manager sets up the project and item owner so a request enters the correct queue.
Review
Producers submit files and renditions, while the Rights Manager checks agreements and version use before the file approval decision.
Release
The Editor publishes an approved item and checks the recorded time and linked task completion.
A content operations team may handle many requests at different points of production. The content item is the working unit: it has a project, owner, due date and state. Production tasks identify the action and person responsible for a particular step. The Business Overview helps the team see the library's status mix and rights that are nearing their end date before assigning the next release.
Begin with one active project and a manageable release cycle. Bring in the items that already have named owners and known due dates. Attach the file revision that will be reviewed, rather than adding an undifferentiated folder of old files. Add rights agreements to the affected items and usage rights to the relevant versions.
Walk a Producer, Rights Manager and Editor through the same item. The Producer should be able to identify the exact revision under review. The Rights Manager should be able to find the agreement party, allowed use and validity interval. The Editor should see an approved parent item before publication and a publish time afterward.
Use the resulting item and task lists in a daily check. Draft and editing work needs production attention; review work needs a decision; approved work needs a release plan. Expiring rights need an owner to resolve the permitted use before another version is published. This routine keeps the operational record useful between launch dates, not only at the end of a campaign.
Features to start with
Roles on the team
- Admin
- Sets up access and reviews cross-project records.
- Content Manager
- Owns the project schedule and checks production handoffs.
- Producer
- Prepares content, versions and production tasks for review.
- Rights Manager
- Checks agreement coverage and records the use allowed for each version.
- Editor
- Reviews the release candidate and publishes approved content.
Set up Digital Asset Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.