Admin
Maintains access and reference records for the publishing team.
Can
- Manage Users, People
- View Projects, Manuscripts, content items, rights agreements, print editions, production tasks, project costs, content files, approval operations
Give editorial, production, rights and finance owners the records they need to act on.
A rights agreement review and a content version approval need an identified person. Bind the approver's People record to their user before the first approval.
Managing Editor prepares content for review; Rights Reviewer checks current coverage and decides the version approval.
Publishing Director owns the title plan. Production Lead follows assigned work, and Finance Lead reviews costs recorded against that title.
| Role | Publishing projects | Manuscript review | Content production | Rights and approval | Print editions | Costs and reporting |
|---|---|---|---|---|---|---|
| Admin | Edit | Edit | Edit | Edit | Edit | View |
| Publishing Director | Edit | View | View | View | View | View |
| Managing Editor | View | Edit | Edit | View | View | View |
| Production Lead | Edit | View | Edit | Edit | Edit | Edit |
| Rights Reviewer | View | View | Approve | Approve | View | — |
| Finance Lead | View | — | View | — | View | Edit |
Maintains access and reference records for the publishing team.
Owns publishing project decisions and reviews the portfolio.
Starts on: Project Pipeline
Assigns editors and manages editorial and content progress.
Starts on: Manuscript Intake Inbox
Coordinates project tasks, content files and edition records.
Starts on: Project Pipeline
Checks agreement coverage and decides content version approval.
Starts on: Content Approval Inbox
Maintains project cost entries and reviews budget exposure.
Starts on: Unsettled Project Costs
Start free, then use Proto to change fields, steps and approvals before your team goes live.