For Labs
Your whole lab, writing together.
Built for researchers working as a group. One shared workspace for every manuscript in flight — with roles, review workflows, a group reference library, lab templates, admin controls, and an audit trail underneath it all.
Shared workspace
Every manuscript in flight, on one screen.
A lab workspace holds the group's projects side by side — who is writing, what stage each paper is at, and what is blocking submission. The PI sees the whole pipeline without asking for status updates; students see exactly where their work fits.
- All lab manuscripts, proposals, and reviews in one shared space
- Stage at a glance: drafting, in review, validated, submitted
- New members get access to ongoing work the day they join
Roles & review workflows
PI sign-off as a workflow, not an email thread.
Owner, editor, reviewer, and reader roles map onto how labs actually work. Sections move through review states — a student submits, a postdoc suggests, the PI approves — and every decision stays attached to the text it concerns.
- Per-project roles with sensible defaults for supervisors and students
- Section-level review: request, suggest, approve — like pull requests
- Suggestions applied as diffs, so approval means exactly what was seen
Group library & lab templates
The lab's references and house style, shared once.
A group reference library keeps the canon of your field resolved, deduplicated, and available to every manuscript. Lab project templates carry your house style, standard sections, and grant boilerplate — so every new draft starts the way the lab writes.
- Shared, DOI-resolved reference collections across all projects
- Repairs propagate: fix a dead DOI once, every manuscript benefits
- Lab templates for articles, proposals, and theses — maintained centrally
Admin, audit & storage
Controls for the lab, without slowing the lab down.
Admins manage membership, set AI policy, and see an append-only audit trail of exports, permission changes, and AI actions. Storage is pooled across the group — 250 GB shared, not sliced into per-person quotas that run out mid-figure.
- Membership and role management with ORCID-linked identity
- Audit trail: joins, permission changes, exports, and AI actions
- 250 GB pooled storage shared across the whole workspace
A day on one manuscript
Three roles, one living paper.
The same manuscript — the lab's sleep-restriction study — over a single working day. No attachments, no status meetings, no version archaeology.
09:10
The PhD student
MR drops the new mixed-effects estimates into §4 of the sleep-restriction manuscript. The consistency check flags that the abstract still says n = 48 while §3.1 now reports 45 — she fixes it in the same sitting, before anyone else has read a word.
11:40
The postdoc
JO diffs §3 against last week's v8, accepts two of MR's suggestions and rewrites a third, and adds a citation for the exclusion criteria — verified against Crossref as he inserts it. His review lands as comments on the exact sentences it concerns.
16:20
The PI
AK opens the workspace, sees 41 of 42 checks passing and one section awaiting sign-off, reads the diff — not the whole paper — and approves §3. She names the version “v9 · Ready for co-author read” and goes back to the grant. Nobody emailed an attachment all day.
Governed, not just shared
The lab’s canon stays curated — and onboarding stops being a project.
A shared library only helps if it stays trustworthy. In Dissertatio, the lab’s reference collections and house templates have maintainers: members propose additions and edits, maintainers approve them, and every change is versioned like the manuscripts themselves. New members inherit all of it the day they join.
- Template and library changes are proposed, reviewed, and approved — no silent drift in the house style
- Reference repairs propagate with review: fix a dead DOI once, approve it once, every manuscript benefits
- New members get the library, the templates, and their default role on day one — set by the PI, logged in the audit trail
Why labs switch
What changes when the lab writes in one place.
No more version archaeology
One living manuscript per paper. The lab stops reconciling final_v7_REAL.docx across inboxes, and the PI reviews the version everyone is actually writing.
Onboarding in an afternoon
New students inherit the lab's templates, reference library, and house style on day one — instead of rebuilding a bibliography from a shared-drive folder.
Integrity you can show
Versioned history, ORCID-linked attribution, and an exportable audit trail back up authorship and research-integrity policies with records, not recollections.
The Lab plan is $18 per user per month, billed annually, from 5 seats — and, like every Dissertatio plan, external collaborators join any manuscript free.
Lab FAQ
The questions PIs ask before switching.
- How do seats work as the lab changes?
- Lab is $18 per user per month, billed annually, with a minimum of 5 seats. Seats are added or removed from the admin panel at any time and billing is prorated automatically — a rotation student joining for one term does not require a procurement cycle.
- Who owns a project when a member leaves?
- Lab projects belong to the workspace, not to the individual account. When a member leaves, an admin reassigns ownership in one step and nothing is lost — the manuscript, its history, and its references stay with the lab. The departing member can export a personal copy of anything they authored.
- Do external collaborators need seats?
- No. Collaborators are unlimited and free on every Dissertatio plan, including Lab. Seats are for lab members who live in the shared workspace; a co-author at another institution joins any manuscript by invitation, at no cost, with full editing access.
- How does pooled storage work?
- The workspace shares 250 GB across all projects — no per-person quotas that run out mid-figure. Admins see usage by project, and heavy assets like imaging data can be trimmed or archived without touching manuscripts.
- What roles exist, and who sets them?
- Owner, editor, reviewer, and reader — per project. Workspace admins set lab-wide defaults (students as editors, supervisors as reviewers with approval rights, for example), and project owners can adjust per manuscript. Every permission change is recorded in the audit trail.
- Can we try Dissertatio before moving the whole lab?
- Yes — the usual path. One or two researchers start on the free plan with a real manuscript, invite their co-authors, and upgrade to a Lab workspace when the group is convinced. Existing projects move into the workspace intact, with history.
Bring your lab together on the Lab plan.
Shared workspace, review workflows, group library, admin controls, and 250 GB pooled storage — $18 per user per month, billed annually. Start free and upgrade when the group is ready.