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.
- Publishing House ERP
- Features
- Rights and approval
Rights and approval
Check the agreement and approving person before a content file version is approved.
OverviewRights Coverage Expiring×
Publishing House ERP · Rights and approval
New
Rights Coverage Expiring
Rights agreements
| Party name | Content | Allowed uses | Starts at | Ends at | |
|---|---|---|---|---|---|
| Party 694 | CI-1057 | AU-398 | 09 Oct | 11 Oct | |
| Party 954 | CI-2002 | AU-152 | 25 Oct | 15 Oct | |
| Party 389 | CI-8534 | AU-820 | 26 Oct | 15 Oct | |
| Party 244 | CI-8539 | AU-793 | 14 Oct | 15 Oct | |
| Party 414 | CI-9337 | AU-841 | 20 Oct | 15 Oct |
6 of 6 records
Party 694Rights agreements · RA-29894
ContentCI-1057
Allowed usesAU-398
Starts at09 Oct
Ends at11 Oct
What you can do
Make approval traceable
Each rights agreement connects a party, allowed uses, start and end dates, and contract to a content item. Content files hold an attached version, upload date, parent content item and approving person. The approval action resolves the actor through the People record bound to a user and checks that current coverage exists for the item. A successful decision links the approving person to the file and moves the content item to Approved.
How the work is organized
- Rights term. Agree who reviews start and end dates and what evidence is needed before an agreement is attached.
- Allowed use. Agree the intended uses for the content before the version comes forward for approval.
- Approver identity. Agree which person may decide and make sure their People record is bound to their user.
What to agree during setup
Start with one real title and name the person who is responsible for the record. Decide who can revise dates or statuses, and when a change needs another person’s review. Check each actual project, manuscript, content or person reference before using that record in a handoff. The agreed practice should be visible in the record, not held only in an email thread.
For each handoff, identify the person expected to act next. Check that their user and People record are connected before relying on an approval decision. Keep the source attachment or agreement with the relevant record when the decision depends on it. This makes the working lists useful during a busy production week.
Check the handoff on an actual case
A content editor uploads a revised file for a project title. The Rights Reviewer opens the content item, checks the attached agreement term and allowed uses, and confirms the version under review is the one to approve. If the term has ended or no covering agreement exists, approval is refused and the reviewer resolves the rights record before another attempt. With current coverage and an identified approver, the approved file names the person who made the decision. A repeated submission of the same approval operation replays its recorded outcome instead of producing another decision.
Before expanding to other titles, ask the people named above to walk through this case in the app. They should be able to point to the current record, explain the next decision and find the owner without reconstructing the history from messages.
What your team sees
- Rights Coverage Expiring — Agreement terms whose end date has arrived or passed.
- Content Approval Inbox — Content in review awaiting the rights and version decision.
Follow the work through
See the related process and the data model for the records behind this handoff.
What it keeps track of
Data model- Rights agreements
- Rights coverage agreements for content items
- Content files
- Versioned file evidence attached to a content item
- Content items
- Individual content units produced within a project
- People
- Staff and contributors of the publishing house
- Approval operations
- Idempotency ledger for content approval workflows: one row per approval operation key, holding the approved outcome so a duplicate submission replays instead of approving twice.
Who uses it
Permissions- Rights Reviewer
- Checks coverage and approves the version.
- Managing Editor
- Prepares the content item and file for review.
- Admin
- Maintains user and People bindings.
Set up Publishing House ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.