> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/end-user-and-partner-section/end-user-section.md).

# End User Section

### Getting Started

* **Login and Navigation:** How to access Docbits and navigate through the interface.
* **Initial Configuration:** Setting up Docbits for first-time use.

### Daily Use

* **Document Submission:** Instructions for submitting documents into Docbits.
* **Document Review and Approval:**
  * **Approving Orders:** Steps for reviewing and approving order forms.
  * **Processing Invoices:** Guide on how to process incoming invoices for payment.

### Managing Documents

* **Search and Retrieve:** How to find and access documents within Docbits.
* **Edit and Update:** Editing documents and updating their status.

### Troubleshooting

* **Common Issues:** Solutions to frequent problems encountered by users.
* [**Support Contact**](https://docs.docbits.com/end-user-and-partner-section/end-user-section/ressources-and-support/user-support.md)**:** How to reach support for assistance.


---

# 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://docs.docbits.com/end-user-and-partner-section/end-user-section.md?ask=<question>&goal=<user_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.
