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.
- Photo Studio Management
- Features
- Rights and review
Rights and review
Check allowed uses and current agreement coverage before approving a file version.
OverviewRights Coverage Watch×
Photo Studio Management · Rights and review
New
Rights Coverage Watch
Rights agreements
| Content | Party name | Allowed uses | Starts at | Ends at | Contract | |
|---|---|---|---|---|---|---|
| CI-3166 | Party 676 | AU-491 | 13 Oct | 15 Oct | CNT-446 | |
| CI-9102 | Party 647 | AU-429 | 24 Oct | 15 Oct | CNT-896 | |
| CI-5296 | Party 831 | AU-401 | 24 Oct | 15 Oct | CNT-992 | |
| CI-5216 | Party 258 | AU-797 | 22 Oct | 15 Oct | CNT-773 | |
| CI-3841 | Party 851 | AU-935 | 16 Oct | 15 Oct | CNT-654 |
6 of 6 records
Party 676Rights agreements · RA-85279
ContentCI-3166
Allowed usesAU-491
Starts at13 Oct
Ends at15 Oct
ContractCNT-446
What you can do
Tie approval to the actual version
A rights agreement records the party, allowed uses, coverage dates and contract attachment for a content item. A content file records its version, upload date, attached file, linked content item and approver. Together they let the Publication Reviewer answer which version was approved and which agreement covered the use at the time. The review decision belongs to a version, not simply to a project or a folder of files.
When a Producer submits a content file version, the Publication Reviewer checks the current rights agreement. Approval of that exact version moves the linked content item to Approved only when coverage is current. If the agreement is outside its dates or the allowed use does not cover the content, the reviewer keeps the item in Review and resolves the rights question before deciding again.
How the work is organized
- Agreement coverage. Each agreement is linked to a content item with party, allowed uses and dated terms.
- Version decision. The reviewer sees the submitted file version and records the approving person against it.
- Content status. Approval advances the linked item only after the rights condition passes.
What to agree during setup
Agree the words used for allowed uses so reviewers can compare an intended delivery with the contract without guessing. Decide who enters agreement dates and who checks the attached contract. A contract may cover multiple uses, but each content item must point to the agreement used for its own decision. The reviewer should check the current date against both the agreement start and end before approving. Check agreement dates directly before a planned delivery; Rights Coverage Watch shows agreements ending today or earlier.
A new file version calls for its own decision. The team should rehearse that an older approval does not substitute for approval of the file now being delivered. The Editorial Manager also checks current coverage at publication, because an agreement that was current during review may expire before delivery.
Check the handoff on an actual case
A studio prepares a client portrait for a campaign. The agreement identifies the client party, an allowed campaign use and a coverage window. The Content Producer uploads a corrected image version and the Producer sends it for review. The Publication Reviewer opens the version, checks the agreement and approves that file while the coverage is current. The item moves from Review to Approved. If the same version is later scheduled for a use outside the agreement, the manager checks coverage again before publication and resolves the contract question before proceeding.
What your team sees
- Rights Coverage Watch — Agreements ending today or earlier for immediate review.
- Content Review Queue — Items needing a version and rights decision.
- Content Items Status Board — Deliverables grouped by lifecycle status without hiding the owner.
Follow the work through
Use review and delivery for the decision sequence. The roles page sets the access rehearsal.
What it keeps track of
Data model- Rights agreements
- Usage rights and contract coverage for a content item.
- Content items
- Individual content deliverables produced under a project.
- Content files
- Versioned file uploads attached to a content item, with approver.
- People
- Studio staff and contractors who own projects, content, tasks and sessions.
Who uses it
Permissions- Publication Reviewer
- , Producer, Editorial Manager and Admin.
- The Publication Reviewer approves the submitted file version; the Editorial Manager checks rights again when publishing.
Set up Photo Studio Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.