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
- Process
- Rights to approval
Rights to approval
This process gives the team a shared handoff for a title. Start with an actual manuscript or project and let each named person find the records they must act on. The status on one record does not stand in for a decision on another.
Step by step
-
Attach agreement Rights Reviewer
Rights Reviewer connects the agreement, party, allowed uses, dates and contract to the content item.
- Rights Reviewer connects the agreement, party, allowed uses, dates and contract to the content item
- Updates Rights agreements, Content items
-
Select file version Managing Editor
Managing Editor identifies the attached file version under review.
- Managing Editor identifies the attached file version under review
- Updates Content files, Content items
-
Check coverage Rights Reviewer
Rights Reviewer checks that an agreement covers the item and remains current.
- Rights Reviewer checks that an agreement covers the item and remains current
- Updates Rights agreements, Content items
-
Approve content version Rights Reviewer
Rights Reviewer makes the version decision through the approval action.
- Rights Reviewer makes the version decision through the approval action. *Human gate.*
- Updates Content files, Content items, People, Approval operations
ApprovalA person approves before the work moves on.
Who does what
Roles and permissions- Rights Reviewer
- , Managing Editor.
- See [roles](/publishing-house-erp/roles) for the working access model.
Set up Publishing House ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.