Core365 products · Publishing
Manuscript to published title, in one system
Core365 Publishing runs the editorial workflow for book publishers — submissions, review rounds, revisions and approval, then titles with validated ISBNs. Multi-tenant, role-based, and audited end to end.
The workflow
Every manuscript follows the same path
Most small publishers run editorial on email and shared drives. Versions get lost, review deadlines slip, and nobody can say who approved what. Core365 Publishing puts the whole path — draft, submit, assign editor, review, revision, resubmit, approve — in one place with the history attached to the manuscript.
Submission to approval
Draft, submit, assign an editor, review, request a Minor or Major revision with a due date, resubmit, then approve or reject.
Versioned uploads
Every file upload is versioned. PDF, Word, RTF, ODT, TXT and EPUB are accepted, and file types are verified by content rather than trusting the extension.
Discussion in context
A discussion thread and full history sit on each manuscript, so the decision trail stays with the work instead of in someone’s inbox.
Authors with or without logins
Author profiles exist whether or not the author has access. When they do, the login is linked to their author record.
Titles and ISBNs
Titles are created from approved manuscripts or entered directly for backlist. ISBN-13 check digits are validated and must be unique. A title cannot be published without one.
Roles that mean something
TenantAdmin, EditorManager, Editor and Author, enforced on the server rather than hidden in the interface.
Platform
Multi-tenant from the ground up
Tenant isolation
Every query is scoped to the tenant, and that isolation is covered by automated tests rather than assumed.
Plan limits
Each publisher has limits on users and titles, set by the platform administrator and enforced in the application.
Immediate effect
Users are re-checked on every request, so disabling a user or suspending a publisher takes effect at once rather than when a session expires.
Full audit log
Logins, failed logins and every create, update and workflow action are recorded.
Account protection
Passwords are hashed with bcrypt, accounts lock for 15 minutes after five failed attempts, and login is rate limited.
Support access
Platform administrators can open a tenant to help with a problem, and that access is logged like everything else.
Questions
Common questions
Who is this built for?
Independent and small-to-mid-sized book publishers who are running editorial on email and spreadsheets and need the workflow, versioning and approval trail in one system.
What is included today?
The editorial workflow end to end: tenants and plan limits, users and roles, author profiles, the full manuscript lifecycle with versioned uploads and discussion, titles with validated ISBNs, and the audit log.
What is on the roadmap?
Contracts and royalties, title metadata and ONIX feeds, then production, title P&L, sales reporting and marketing. We are happy to talk through timing against what you need.
Can we migrate existing titles?
Yes. Backlist titles can be entered directly rather than going through the manuscript workflow, so your existing catalogue sits alongside new acquisitions.
What file types can authors submit?
PDF, Word, RTF, ODT, TXT and EPUB. Each upload is checked by its actual content, so a renamed file will not slip through.
Where is it hosted?
Hosted by Core365, or deployed on your own infrastructure if you have data residency requirements.
See the editorial workflow end to end
Book a demo and we will walk a manuscript from submission through review to a published title.