Three page types
Standard, blog and canvas live in the same tree and carry the same permissions
Write at the same time
Several people on the same page, with nobody overwriting anybody
Every version stays
Leaving the editor creates a version you can restore later
Permissions per page
A single page can be restricted without closing the whole space
When the valid version travels as an attachment.
The concept sits as a file in an inbox, the remarks on it across three replies, and the last change was saved on somebody's laptop. Anyone looking for the valid version asks for the date. A page has exactly one valid version, and everything before it stays next to it.
Two versions of the same document are in circulation, and both have been edited.
Remarks on the text sit in email instead of next to the paragraph they are about.
One document has to stay closed to part of the staff while the space stays open.
What you gain.
An editor that stays out of the way
Headings, lists, task lists, tables, code, callouts, images and embeds all sit behind a slash. Standard pages carry prose, blog pages a date and an order, canvas a free drawing surface. Each page sets its own width, from narrow for long text to full for wide tables.
At the same time, without a conflict
Several people edit the same page and see each other's changes as they are typed, along with named cursors and the avatars of everyone currently on the page. Two edits to the same sentence are merged instead of one overwriting the other. If the service is unavailable, editing continues with a single writer, so nobody meets a locked page.
Versions, comments and suggestions
Every edit leaves a version with its author and timestamp. When you restore one, Collabase saves the current state first, so nothing is lost. Comments hang off a paragraph or the foot of the page and carry their visibility. Someone with read access proposes wording, and the owner decides on it.
Templates and per-page permissions
Recurring documents start from a template: structure, subheadings and placeholders that are filled in on creation. Permissions are set on each page independently of the page above it, and a PDF export takes title, text and tables with it.
Who this pays off for.
Operations manuals
One procedure, one page, and last week's version still sitting next to it.
Meeting records
A template with attendees, agenda and decisions, written together during the meeting.
Specifications
The business side proposes wording while responsibility for the text stays in one place.
HR and legal
Individual pages stay restricted while the space remains open to everyone.
Documents belongs to the platform.
A page lives in a space, next to the projects of the same team. It points at work items, holds registry records as a field, and the automation engine reacts to every new page and every comment. All apps share login, permissions and data. One licence, one deployment, one point of contact.
Docs
Projects
Intranet
Registry
Test Management
Automation
Time
Operations and data sovereignty.
Where the data sits is decided by the operating model, not by the small print.
Swiss hosted
Operated on Swiss public cloud at Infomaniak, one isolated environment per customer. Content is processed in Switzerland only, apart from the upstream web application firewall.
Self-hosted
Runs on your own infrastructure. Full control over the data, no access from outside.
revFADP & GDPR
Data processing agreement included. Compliant with the revised Swiss data protection act and the GDPR.
One licence, all apps.
Collabase Enterprise
On request
Staged by user count
Documents is part of the Enterprise plan. All seven apps, no add-ons.
Bring your manual
into one valid version.
In the proof of concept we set up the tree, the templates and the permissions for your area, with your own documents.