> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/my-company/groups/how-to-create-a-group.md).

# How to create a group

Groups in equipme help you structure people in a way that reflects how work actually happens inside your organisation. Whether you operate departments, project teams, or temporary task forces, groups give you a place to cluster people, make responsibilities visible, and connect them to workflows.

You don’t have to overthink it upfront. Most organisations start with a handful of groups that mirror their basic structure and refine things as they learn how equipme supports their daily work.

<figure><img src="/files/j1g7nQnzykLsCBsrfIvv" alt=""><figcaption></figcaption></figure>

### Where to create a group

You can create a group in a few steps:

1. Go to **My Company**
2. Select **Groups**
3. Click **New**

This opens a simple form where you define the group. The fields are straightforward, and you only need the essentials to get started.

<figure><img src="/files/EsjySkv0D5e5iKBOcI6q" alt=""><figcaption></figcaption></figure>

At a minimum, each group needs a **name**.\
Everything else is optional and can be added later.

If you want, you can also link the group to a company, assign a general type, add a contact address, or leave notes that make it easy for others to understand what the group is about. None of these decisions lock you in permanently.

Groups are flexible and can be edited or repurposed at any time.

<figure><img src="/files/qTnLkrzg9PqS2P5olRzg" alt=""><figcaption></figcaption></figure>

### Choosing a group type

The *Type* field is more than a label. It describes what kind of group you are creating and gives equipme context for how the group fits into your company structure.

There are several types to choose from:

**Department**\
Used for functional structures such as Sales, HR, IT, Finance.\
This is the most common choice because departments usually control budget and approvals.

**Project**\
Useful for temporary initiatives with a defined objective or timeline.\
Project groups make it easier to track activity and cost outside traditional hierarchy.

**Team**\
Smaller operational units that work together inside a department or project.\
Helpful when teams have their own tasks or equipment, even if they report upward.

**Company**\
Used when you manage multiple companies or legal entities in one tenant.\
This option is relevant when services, ownership or accounting differ between entities.

**Custom**\
A flexible option if none of the predefined types fit what you are doing.\
This keeps things open without assigning default assumptions.

Choosing the right type does not change functionality in a technical sense, but it helps later when you want to filter data, review reports or understand where responsibilities sit.


---

# 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://hub.equipme.io/equipme/my-company/groups/how-to-create-a-group.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.
