Canonical page: https://tellenze.com/help/knowledge

# Write, discuss, and organize knowledge

Create documents and folders, discuss passages, inspect revisions, and link decisions to work.

## Find the right home for knowledge

**Knowledge** in the workspace sidebar opens your team's document library: decisions, runbooks, research, and delivery outcomes. The library starts with your **Pinned** items, workspace and project locations, and **Recently updated** documents. It does not automatically open a document or remember the last project you visited.

Open **Workspace** for shared guidance or a project for documents that belong with its work. Open folders one level at a time and use the breadcrumbs to return to a parent location. Opening a document gives it a focused reader; **Back to library** returns to the location or search you were browsing. Browser back/forward and links preserve that location.

On mobile, **Browse locations** initially shows your favourite projects. If you have none, it shows up to three locations. Choose **Show more locations** to see the rest, or **Show fewer locations** to collapse the list again. The full list stays visible on wider screens.

Search includes document content as well as titles, with location labels and matching excerpts. Use **All knowledge** to search everything you can access or choose a specific workspace/project scope. Recently updated is always ordered by the latest update; it has no manual sorting controls.

Inside a project, the **Documentation** tab loads the first group of pages before fetching the rest in the background. You can start reading and editing while **Loading more documents…** is visible; search results and folder counts fill in as pages arrive. If loading stops, choose **Retry loading documents** to continue without losing the pages already open.

Workspace documents are available to active workspace members; project documents follow project access. Folders organize pages within a scope and do not grant extra permissions. Your team documents remain separate from this public Help center.

## Keep useful documents and folders close

Choose the pin icon beside a document or folder, or **Pin** in the reader, to add it to **Pinned** on the library home. Pins are personal and follow your account across sessions. Open a pinned folder to browse its contents or a pinned document to read it. Choose **Unpin** to remove the shortcut without moving or deleting the item. Archived items and items you can no longer access are hidden from your pins.

## Create and edit a document

1. Choose **New document**. Enter a title, choose its **Location** and **Folder**, then **Create document**. **Unfiled** leaves it outside folders. When browsing a location or folder, creation starts in that location. When creating from a project's documentation area, the project is already selected.
2. Write the **Document body** in Markdown. Use headings, lists, links, and code blocks to make the guidance readable. The work-item link picker helps connect your text to relevant work.
3. Choose **Save** in the toolbar or **Save document** below the editor. Each saved version becomes an immutable revision. Use **Edit** for later changes and **Copy link** to place the canonical document on the work that needs it.

Editing requires access to an active document and, for project documents, an active project. If saving reports that someone edited first, inspect the latest saved version before saving again. Do not assume your earlier draft still describes the latest content.

## Organize folders and move pages

Choose **New folder**, name it, and select its location and **Parent folder**. Folders can be nested. Open a folder to browse its pages; use its actions menu to **Rename**, **Move to…**, or change its position with **Up** and **Down**. Dragging within a location also supports folder and document placement, while the menus provide an alternative. In a project's documentation panel, folders still expand inline.

Deleting a folder moves its documents and child folders up one level; it does not delete their contents. A document can be moved into another folder or left unfiled. Use a document's move action to change its location when you have the appropriate access.

Before a move broadens the audience, the move dialog explains who gains access and asks you to **Confirm audience change and move**. This applies to the document, its past revisions, and attached files. Moving preserves the document's links and history, so review the destination carefully.

## Discuss a document or a passage

Choose **Comments** to open the discussion drawer, then **New comment** to ask a question or leave a note about the whole document. No selected passage is required. To discuss specific wording, select text in the rendered document and choose **Comment on selection**. Write the comment, optionally select members to mention, and **Add comment**.

The drawer is closed by default so the document has room to read. Passage markers and direct discussion links open the relevant thread. Open discussions appear first; enable **Show resolved discussions** to include closed threads. Use **Reply**, **Resolve**, or **Reopen** as the conversation progresses. Passage anchors stay attached across compatible revisions; **Anchor changed** means the original passage no longer matches, while the discussion retains its quotation for context. General document discussions remain available after the text changes.

Where **Create work item** is available on a project document's discussion, it creates linked follow-up work in that document's project with the discussion context and source passage, when there is one. The thread then links to the resulting work item. This does not share the document outside its existing scope.

## Inspect revisions and attach evidence

Open **Details** beneath the title to distinguish who created the document from who last updated it, with dates and the latest version number. When an agent or system was involved, its name appears under the relevant event.

Choose **History** to inspect saved versions, authors, dates, and recorded origin in an expanded reading dialog. Select a version to preview its title and body; use **Load older** for earlier entries. A history preview does not replace the current document. To reuse older wording, deliberately edit and save the current page.

Under **Reference files**, choose **Attach file** to add supporting evidence. Uploaded images show a preview once available; select it to open the full image in a new tab. Download a file from its entry when available. A file marked **scanning** is not yet downloadable or previewable. Removing a file asks for confirmation because the file cannot be restored through that action.

## Keep guidance useful over time

Link canonical documents to the work they explain and revise them as decisions change. **Archive document** removes an outdated page from active documentation while retaining revision history. Check scope, filters, archive state, and project access when a page seems missing; copying its URL does not bypass permissions.

Where **Required Context** is enabled, policies can pin particular document revisions for agent reading. Updating this document does not automatically update a published policy's pin. Review the dedicated **Required Context** guide when changing mandatory reading or assigning procedures.