Notes & Docs

Your company's documentation in one place: private notes, notes shared with colleagues, and wiki pages in spaces with a page tree, versions, templates and a review cycle.

Overview

Everything is written in a visual editor (Markdown underneath: headings, lists, tables, task lists, code, pictures and draw.io diagrams). Notes save themselves a few seconds after you stop typing. Ctrl/Cmd+S saves at once, Ctrl/Cmd+E switches between reading and editing, Ctrl/Cmd+. opens the note's settings.

The one question that matters is: who can read this, and who can change it? The answer depends on where the note lives.

1. Where a note lives

Personal notePage in a space
What it isA note you wrote, in your list.A wiki page in a space (for example one per team, project or topic), arranged in a tree.
Who decides who readsThe owner, per note.The space's access list, not the page.
Who writesThe owner, and people the owner named as editors.Everybody with edit or admin level in the space.
Starts asPrivate.A draft only its author sees, until published.

The owner is the person who made the note (or a person it was handed over to). The owner can always read and edit it.

2. Personal notes: who reads, who writes

In the note's settings (or in the New note dialog, or the right-click Share), the owner sets Who can read it:

SettingWho can readWho can write
Privateonly youyou
Teamsthe members of the teams you chooseyou
Projectsthe members of the teams that belong to the projects you chooseyou
Peoplethe people you name under can readyou, and the people you name under can read and edit
Everybodyevery user of the instanceyou

3. Spaces and pages

A space has a short key (such as ENG), a name and an access list. The list names users, teams or everybody, each at one level:

LevelCan do
Readread pages and their history
Editread; create, write, move and publish pages; add pictures; use and save templates; restore versions
Admineverything an editor can, plus delete and archive pages, change the access list and the space's settings, see the space health

4. Who may do what

You do not have to work this out yourself: the Access button (shield icon) in the toolbar of every note shows where it lives, who can read it, who can write it, and what you may do with it and why.

Personal: ownerPersonal: named editorPersonal: readerPage: space readerPage: space editorPage: space admin
Read, view history and versionsyesyesyesyesyesyes
Change title and text, add picturesyesyes--yesyes
Restore an older versionyesyes--yesyes
Change who reads ityes--space admin only (the access list)-yes
Set tagsyes---yesyes
Review, set validity, hand overyes--the page's owner
Archive a page----the page's owneryes
Deleteyes---the page's owneryes

Two things never change the picture: a note's folders are each person's own bookmarks and give nobody any access, and an archived page is read-only for everybody.

5. Keeping content current

Documentation rots. Notes & Docs keeps stale content out of the way instead of letting it pile up.

6. Templates

For pages that should look the same everywhere (project pages, system documentation, meeting notes): write one page, right-click it and choose Save as template. Choose whether it is for one space (its editors use it) or for everybody (the RC Admin's choice). In the title and text, {{date}}, {{author}} and {{space}} are filled in when a page is made.

7. History and versions

Everybody who can read a note sees its activity (created, edited, shared, handed over, reviewed, archived...) and its versions with a line-by-line comparison, as in a wiki. Saves by one person within 15 minutes are one version. Restoring an old version (editors and owners) is itself a new version, so nothing is lost. Deleting a note deletes its history.

8. Folders, tags, pictures, encryption

Rules and limits