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

# My company

My company: map locations, groups, employees, cost centers and billing addresses in equipme.

The **"My company"** section of the sidebar (group **"Company"**) maps the structure of your company. It is the foundation for everything else: who a service is assigned to, who approves orders, which cost center is charged and where deliveries go.

| Menu item                                                   | Content                                                                          |
| ----------------------------------------------------------- | -------------------------------------------------------------------------------- |
| [**"Locations"**](/dokumentation/organization/locations.md) | Offices, branches and warehouses with address, cost center and location managers |
| [**"Groups"**](/dokumentation/organization/groups.md)       | Organizational units: departments, teams, projects, companies                    |
| [**"Employees"**](/dokumentation/organization/employees.md) | All employees with profile, services, user account and permissions               |

In addition, this area includes:

* [Cost centers and billing addresses](/dokumentation/organization/cost-centers-and-billing-addresses.md) (under Settings → "Company profile")
* [Onboarding and offboarding](/dokumentation/organization/employees/onboarding-and-offboarding.md)
* [Import employees](/dokumentation/organization/employees/import-employees.md) and [HR sync](/dokumentation/organization/hr-sync.md)
* [Further information (custom fields)](/dokumentation/organization/additional-information.md)

**"My organization" manager menu:** Supervisors only see the employees reporting to them under "Employees"; location managers only see their own locations under "Locations".

## Recommended order for the setup

1. Create **billing addresses** and **cost centers**.
2. Create **locations** (with address and cost center).
3. Create **groups**, especially departments if department managers are to approve.
4. Create **employees**, import them or take them over via HR sync, with location, department, supervisor and cost center.
5. Assign roles and invite employees.

{% hint style="info" %}
If your company uses an HR system that equipme supports, the [HR sync](/dokumentation/organization/hr-sync.md) takes over employees, locations, departments, supervisors and cost centers automatically. Steps 2 to 4 then largely become unnecessary.
{% endhint %}

## Terms that are often confused

| Term                                                  | Meaning                                                                                   |
| ----------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| **Supervisor**                                        | The person directly above an employee. Entered on the employee and independent of groups. |
| **Department manager**                                | Whoever has the group role "Manager" or "Deputy Manager" in a group of type "Department". |
| **Location manager** ("Location manager (purchaser)") | May order and approve for their locations.                                                |
| **Location manager (planner)**                        | May manage services of their locations, but may not order or approve.                     |
| **Cost center manager**                               | Whoever is entered as manager on a cost center.                                           |


---

# 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://hub.equipme.io/dokumentation/organization.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.