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
- Features
- Rights coverage
Rights coverage
Keep agreements and version-level usage terms visible at review.
OverviewRights Agreements List×
Digital Asset Management · Rights coverage
New
Rights Agreements List
Rights agreements
| Id | Party name | Allowed uses | Starts at | Ends at | Content | |
|---|---|---|---|---|---|---|
| IDD-231 | Party 250 | AU-351 | 11 Oct | 15 Oct | CI-9608 | |
| IDD-524 | Party 802 | AU-611 | 04 Oct | 12 Oct | CI-2834 | |
| IDD-603 | Party 336 | AU-879 | 03 Oct | 07 Oct | CI-7605 | |
| IDD-810 | Party 663 | AU-584 | 12 Oct | 15 Oct | CI-2930 | |
| IDD-434 | Party 350 | AU-397 | 17 Oct | 15 Oct | CI-5862 |
6 of 6 records
IDD-231Rights agreements · RA-84850
Party nameParty 250
Allowed usesAU-351
Starts at11 Oct
Ends at15 Oct
ContentCI-9608
What you can do
Put the permitted use beside the asset
A rights agreement is attached to a content item. It records the other party, the allowed uses, a start and end date, and the contract attachment. Usage rights sit closer to a specific media version, with a licensee, allowed use and validity interval. Together they let the Rights Manager examine both the agreement for the content and the terms under which a rendition may be used.
The version approval workflow checks rights coverage when the exact file revision is reviewed. The usage rights workflow validates its linked media version and date interval and writes an attributed review state back to the media record. These checks make the links between agreement, item, version and proposed use important. A correct date on an unrelated agreement does not answer whether this asset can be released.
How the work is organized
- Agreement. The Rights Manager links the signed contract and permitted uses to the content item.
- Version use. The Rights Manager records the licensee, allowed use and dates for a media version.
- Decision. The approving reviewer considers coverage before the file revision can approve its parent item.
What to agree during setup
Agree how the team phrases allowed uses so a reviewer can understand them without opening the contract for every routine check. The contract attachment remains the source document when terms need interpretation. Decide who records a new agreement, who checks an amendment, and when a usage right should be attached to a new rendition rather than reusing an older version’s terms.
Choose an operating rule for approaching end dates. The Business Overview surfaces expiring rights, and the rights lists can help the Rights Manager work through them. A useful review should identify the affected content item or version, the licensee or party, and the date that changes the decision. The team should agree who contacts the counterparty before another publication depends on an expiring permission.
Check the handoff on an actual case
A Producer prepares a new cut of a campaign video. The Rights Manager opens the agreement attached to the content item and reads the allowed uses and contract interval. A usage right for the new version names the licensee and a narrower channel use. The Producer submits the rendition for review. The reviewer checks its use terms and the item agreement, then checks the separately linked file revision before approval.
If the new cut is scheduled beyond the agreement end date, the team should address the agreement before approval. If the agreement permits the date but the version’s usage right covers another channel, the Rights Manager should resolve that distinction as well. The important handoff is a decision on the actual item and rendition, with the supporting rights records linked to them.
After publication, keep the same relationships available for a later inquiry. A manager should be able to find the published item, follow its rendition to the usage record, and open the agreement attached to the item. This is also how the team can identify assets affected by a rights interval coming to an end.
What your team sees
- Rights Agreements List — Work through item agreements that have ended or end today.
- Usage Rights List — Inspect permitted uses and expiration by media version.
- Rights agreement schedule — Compare start and end dates for agreements that have ended or end today.
Follow the work through
See rights review and content review.
What it keeps track of
Data model- Rights agreements
- Rights and licensing agreements covering content items.
- Usage rights
- License and usage rights granted for a media version.
- Content items
- Individual content items produced within a project.
- Media versions
- Versioned media renditions captured for a content item.
- Content files
- File revisions attached to a content item, with approving reviewer.
Who uses it
Permissions- Rights Manager
- , Editor, Producer, Content Manager, Admin.
Set up Digital Asset Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.