Choose a space
Open "Knowledge base" and select your personal space or a project. You can use the personal space for your own notes. Creating project pages requires permission to edit that project's knowledge base. Creating or changing content also requires an active seat. Existing pages have their own access lists.
Choose "New page" and enter a title and body. For a nested page, open the parent's actions menu and choose "New child page". Use the tree to organize instructions. Search checks titles and bodies of accessible, unarchived pages in the selected space. Pages shared with you also appear under "Shared with me".
For example, create "Release checks" in a project and add "Registration check" beneath it. Both pages appear in the selected project's tree.
Drafts and publication
Write the body with Markdown. A title is mandatory and allows up to 255 characters; the body allows 200000 characters.
For a new page, the menu beside the publish button offers "Save as a draft". This saves a draft in Quevell that only its author has access to, even if other people are already listed for access. Publication activates that access list. The editor does not turn a published page back into a draft.
Your browser saves your unsaved changes locally as you type. After restoring them, publish the changes to save them in Quevell. For a new page or an existing server draft, you can also choose "Save as a draft". That option is not available for a published page. A local edit is not published for colleagues and is not guaranteed to appear on another device. Clearing browser data can remove the local copy.
If someone published a change while you were editing, Quevell reports a conflict. Compare the current version with your text before saving again.
Who can read and edit
Open "Who can open it" in the page menu. The author has access to their page. You can grant people or groups read or edit access. Anyone who can edit the page can also change its access list, so consider that when sharing it.
- Select a person or group.
- Choose "Can read" or "Can edit" and add the entry.
- Ask the recipient to open the published page's link to check the result.
Project membership alone does not replace the page access list. Child pages have their own access too: a position in the tree does not automatically inherit the parent's grants. A draft remains private to its author until publication. When removing access, check whether another group still grants it.
Link an issue
In the page editor, add the key of an issue you have access to and save the page. The issue appears on the page, and the issue's knowledge section links back to the page.
Adding a link requires edit access to the page and access to the issue. The link grants no new permissions. Page readers see only accessible issues; issue readers see only accessible pages. If a link is not visible to a colleague, check their access to both objects first.
History and corrections
Choose "History" from the page menu, then open a saved version to read its earlier title and body. A change to the title or body creates a text revision. Saving an unchanged title and body does not create another revision. Updating access is not a new text version either.
To restore a complete version, choose "Restore this text". Its title and body open in the current page editor. Review them and choose "Publish" to save the correction. To reuse only a passage, copy it from history into the editor manually. Restoring text does not roll back access lists or issue links.
Archive, restore and delete
A page editor can archive the page together with its children. Show the archive in the tree, select the page and choose "Restore from the archive" to bring it back. Restoration also affects its subtree.
Permanent deletion is separate from archiving. Move or delete child pages first, then confirm deletion. This removes the page, text history, access list and issue links. There is no product recycle bin for restoring a permanently deleted page. Use the archive when you only want to set a page aside.
Download the text
Choose "Download .md" from the page menu. The browser saves the title and body of the open page as Markdown. With the editor open, it exports the editor's current text, including edits that have not been published. Save first when you need the published version specifically.
The file does not include the page tree, access list, history or structured issue links. It is a text export; see Data export for transfer limits.