Documents

Documents are Bnder's knowledge-base objects. Use them for decisions, process notes, reusable answers, project context, internal runbooks, and public help content.

Documents live inside a project. They can be grouped into topics, but a document does not need a topic to exist.

Common workflows

Use documents when you want to:

  • keep project knowledge near tasks, tickets, files, and calendar work
  • write internal notes with Markdown formatting
  • link related tasks, tickets, and other documents
  • publish selected documents on your Bnder Pages domain
  • turn closed ticket conversations into reusable knowledge drafts

Organize documents with topics

Topics are optional folders for documents inside a project.

Example:

Project 1
    Topic 1
        Document 1
        Document 2
    Topic 2
        Document 3
Project 2
    Topic 3
        Document 4

Use topics when a project has enough documents that a flat list becomes hard to scan. See Topics for topic commands and structure.

Markdown formatting

Documents support common Markdown formatting.

Headings

Use up to three heading levels:

# Heading 1
## Heading 2
### Heading 3

Bold and italic

**Bold text**
*Italic text*
***Bold and italic text***

[Link text](https://www.example.com)

Images

![Alt text](https://www.example.com/image.png)

If you want to use images in a public document on Bnder Pages, upload the image to File storage, make it public, copy the public URL, and use that URL in the document.

Linking documents to work

Documents can hold project context for tasks, tickets, and events. When related work is linked, teammates can move from the task or ticket into the supporting document without searching through the workspace manually.

For ID-based cross-links, see Object linking.

Publishing public documents

Public documents use Bnder Pages. A public document can be opened from your workspace page domain, such as:

https://company.bnder.page/doc/{document_id}

See Public Documents for draft and publishing behavior.

Creating documents from closed tickets

Agents can create a prefilled document draft directly from a closed ticket (resolved or rejected) using Create knowledge draft in ticket detail.

The draft includes a structured summary template and a related ticket reference. After the first save, Bnder links the new document back to the source ticket.

Commands

Discord workspaces can also manage documents through the Knowledge Manager bot:

Create a document

Opens a dialog to create a new document with title and content.
/document create
Knowledge Manager
Requires MANAGE_DOCUMENTS permissions

Read a document

Displays the content and title of a document
/document read
document
my document
Knowledge Manager
Requires READ_DOCUMENTS permissions

Get Document info

Displays meta information about a document. This includes creator, creation date, last edit date and more.
/document info
document
my document
Knowledge Manager
Requires READ_DOCUMENTS permissions

List all documents

/document list
project
my project
label
my label
Knowledge Manager

Edit a document

Opens a dialog box where the title and content of a document can be edited.
/document edit
document
my document
Knowledge Manager
Requires MANAGE_DOCUMENTS permissions

Delete a document

Provides a confirmation message where a document can be moved to a trash bin or deleted permanently.
/document delete
document
my document
Knowledge Manager
Requires MANAGE_DOCUMENTS permissions

Restore a document

Restores a document from the trash bin.
/document restore
document
my document
Knowledge Manager
Requires MANAGE_DOCUMENTS permissions

Change the topic of a document

Changes the topic of a document. This is useful to group documents by topic.
/document topic
document
my document
topic
my topic
Knowledge Manager
Requires MANAGE_DOCUMENTS permissions