Topics
Topics are optional folders for knowledge documents inside a project. Use them when a project has enough documents that a flat list becomes hard to scan.
Documents can also stay outside a topic, so you can start simple and add topics only when the project needs more structure.
How topics work
Each topic belongs to one project. A project can have multiple topics, and each topic can contain multiple documents.
Project 1
└── Topic 1
└── Document 1
└── Document 2
└── Document 3
└── Topic 2
└── Document 4
└── Document 5
└── Document 6
Project 2
└── Topic 3
└── Document 7
└── Document 8
└── Document 9
Create and manage topics
In Discord workspaces, use topic commands to create, list, rename, move, delete, and restore topics.
When creating a topic, choose the project it should belong to. If you do not choose a project, Bnder uses the currently selected project where that command supports it.
Put documents into topics
Use topics to group documents by area, customer, process, team, or release.
A document can be moved into a topic, moved to another topic, or removed from its topic without deleting the document. See Documents for the document workflow.
Moving, deleting, and restoring
Moving a topic to another project also moves the documents inside it.
Deleting a topic gives you a choice: move the topic and its documents to the bin, or delete it permanently. Topics in the bin can be restored with their documents.
Limits and permissions
Topic limits depend on the workspace plan. See Limits.
Creating, renaming, deleting, restoring, and moving topics requires the MANAGE_TOPICS permission. See
Permissions.