> 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/classes/admin/locations/create-a-location.md).

# Create a location

{% @arcade/embed url="<https://app.arcade.software/share/c3E2qz9iQ9pCWAbXoQiX>" flowId="c3E2qz9iQ9pCWAbXoQiX" %}

Your company address is already a location. It came from the portal setup, so the list is never empty when you open it for the first time. What you create here is everything after that: a second office, a warehouse, a site in another country.

Only a handful of fields are required, and the address is the one that matters. It is where deliveries for this site will go, so an incomplete address surfaces later as a delivery problem rather than a data problem.

Many organisations never create locations by hand at all. If you use [HR Sync](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/settings/integrations/hr-sync-overview), your sites come from your HR or identity system and stay aligned with it automatically.

{% hint style="info" %}
**Coming from Microsoft Entra or another identity system?**

These systems are built to manage accounts, not offices. A person's location is usually a single text value on their account, and there are no dedicated fields behind it for street, postal code or city.

So the site name arrives and the location is created from it, but there is no address to import. The site exists, employees are assigned to it correctly, and the address line stays empty until someone fills it in.

That is worth checking right after your first sync, because a delivery needs a real address. It is a one time correction per site, not ongoing maintenance.
{% endhint %}

### Read more

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/pYjwX1nInR812ah4rHNS" %}
[Locations](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/locations)
{% endcontent-ref %}

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/R4hXo0F6vVhTLlnhrrXi" %}
[Importing locations through HR Sync](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/locations/importing-locations-through-hr-sync)
{% endcontent-ref %}

### Next

A site can do more than receive deliveries: [Location templates](/classes/admin/locations/location-templates.md).


---

# 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/classes/admin/locations/create-a-location.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.