> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.11/development/portal/portlets/document-list.md).
# Document list
The Document list displays the documents stored in the internal document management database. It can be connected to the Document Tree portlet to display all documents contained inside the selected folder in the Document Tree portlet.
### Basic Data
**Internal name** - Unique string to identify this portlet.\
**Portlet title** - Title of the portlet, does not have to be unique.\
**Include subfolders** - Allows the portlet to include subfolders and their content of the document tree.\
**View Documents** - Not yet implemented.
### Auto Refresh
Auto Refresh enables the portlet to refresh the data every SS:second.
#### Query Configuration
**Start node value** - todo.
**Page Size** - Amount of results showed per page.
### Commands
Commands enables the portlet to listen for events sent by other portlets to execute specified commands. **The portlet will listen to the following commands**
* updateDocumentManagementList
**The portlet will listen to the following portlets** *Specify which portlet the commands above will trigger from*. The portlets that appears will be shown with their unique internal name.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.novacuraflow.com/6.11/development/portal/portlets/document-list.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
