Panduan ini berbahasa Inggris. Aplikasi menggunakan bahasa pilihan Anda.
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.
If an existing document cannot load within the request timeout, the app explains the failure and offers Retry without closing the document tab.
Create your first document
- Open the project's knowledge area and choose to create a document. Select a topic if you want to group it with related documents.
- Enter a title that tells readers what the document helps them do, then write the content.
- For a new private document, select Create Document. Existing private documents use Save Changes.
- To publish a public document, use Save and Publish and check the resulting public page. Review Public Documents before publishing internal information.
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***
Links
[Link text](https://www.example.com)
Images
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
When you have CRM access, use CRM links while editing a document to associate it with people, organizations, or records. The document then appears in those customer timelines; public document views never expose these internal links.
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.
Delete or restore documents
Active documents move to the bin and remain recoverable for 30 days. Permanent deletion is available only from the bin and cannot be undone.
Commands
Discord workspaces can also manage documents through the Knowledge Manager bot:
Create a document
Read a document
Get Document info
List all documents
Edit a document
Delete a document
Restore a document
Change the topic of a document