> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/app-components/groups.md).
# Groups
Use groups to divide app modules into logical blocks and to change the order of modules in the GUI.
## Default groups
When creating a new app, new modules are automatically added to the `Other` group. If you've never used this feature in your app before, all of your modules will be placed in this group by default and displayed in categories based on their function.
{% tabs %}
{% tab title="Occurrence in the module" %}
{% endtab %}
{% tab title="Source" %}
```json
[
{
"label": "Other",
"modules": [
"createTask",
"updateTask",
"getTask",
"listTasks",
"listNotes",
"watchTasks",
"watchNotes"
]
}
]
```
{% hint style="info" %}
When there's only a single `Other` group, the modules are grouped according to their type.
{% endhint %}
{% endtab %}
{% endtabs %}
## Change the groups and order
By changing the **Groups** file, you can set up as many groups as you want and group the modules into logical blocks. Once you create a new group and put a single module there, your app will no longer use the default grouping.
{% tabs %}
{% tab title="Occurrence in a module" %}
{% endtab %}
{% tab title="Source" %}
```json
[
{
"label": "Notes",
"modules": [
"watchNotes",
"listNotes"
]
},
{
"label": "Tasks",
"modules": [
"watchTasks",
"createTask",
"updateTask",
"getTask",
"listTasks"
]
}
]
```
{% hint style="info" %}
The modules are displayed **in the same order** as they are specified in the Groups section.
{% endhint %}
{% endtab %}
{% endtabs %}
For the recommended order of groups and modules, see the best practices for [groups](/custom-apps-documentation/best-practices/naming-conventions/groups.md).
One module can belong to one or more groups, but it has to belong to at least one. You won't be allowed to save the group's configuration otherwise.
{% tabs %}
{% tab title="Source" %}
```json
[
{
"label": "Notes",
"modules": [
"watchNotes",
"listNotes"
]
},
{
"label": "Tasks",
"modules": [
"watchTasks",
"createTask",
"updateTask",
"listTasks"
]
}
]
```
{% hint style="info" %}
This code produces the error: `Not categorized module(s): getTask`
{% endhint %}
{% endtab %}
{% endtabs %}
---
# 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://developers.make.com/custom-apps-documentation/app-components/groups.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.
