> For the complete documentation index, see [llms.txt](https://documentation.civalgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.civalgo.com/documentation/settings/tasks-structure.md).

# Tasks structure

## Prerequisites

None

### Creating a task and its subtasks

1. **Add a new task**
   * Click at the top right on **“Create a new task”**.
   * Please fill in the following information:
     * **Task code (optional)** : You can add a code linked to your accounting system.
     * **Task name** : Define the name that will represent this task.
     * **Unit of measure** : Choose a general unit that will include all associated subtasks.
2. **Add subtasks**
   * A default subtask list is already available.
   * To add a new subtask, click **“New subtask”**.
   * Please fill in the following information:
     * **Sub-task name**
     * **Unit of measure** (it may differ from that of the main task)
     * **Sub-task code** (optional)
   * Once you've completed this information, confirm the addition to add the subtask to your list.

### Editing and archiving tasks and subtasks

**Modification:**

* Click the pencil icon to edit an existing task or subtask.

**Archiving:**

* You can archive one or more tasks when they are no longer in use.
* To consult archived tasks, use the menu represented by **Three small dots**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.civalgo.com/documentation/settings/tasks-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.