> 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/tasks.md).

# Tasks

Follow an assigned task with an ordinary test account: inspect the document, record the result, complete the task, save and reload.

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/document-tasks-customer/v1/en.mp4>" %}
Tasks
{% endembed %}

[Watch with subtitles](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/document-tasks-customer/v1/en.html)

The recording shows the actual test interface. Configured values and technical labels retain their original meaning.

Use the task overview to find assigned work and follow its progress. The board groups tasks by status; the list provides more detail. Filter by assignment and use search to locate a particular task. Priority and deadline help plan the order of work.

## Work on an assigned document task

1. Open a task and read its description and assignment.
2. Inspect the linked original document. A task title alone does not prove that the document is correct.
3. Set the task to in progress and save while doing the work.
4. Record the result in the task description.
5. Complete the task, save it and reload to confirm the stored status and feedback. Check its position in the task overview.

The video uses an ordinary test user and synthetic documents. Completing a task is separate from approving or exporting its invoice. Available actions depend on the account's permissions.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-09471bd28c8ff0d83d0e839e5918c287de9fc9a5%2Fcustomer-overview-en-91b31c626e68.png?alt=media" alt="Task board with synthetic demonstration data."><figcaption><p>Task board with synthetic demonstration data.</p></figcaption></figure>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-8bdb78f77ba27ee6d7b9100410ce57decf3668b9%2Fcustomer-find-en-91b31c626e68.png?alt=media" alt="Task list with synthetic demonstration data."><figcaption><p>Task list with synthetic demonstration data.</p></figcaption></figure>


---

# 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/tasks.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.