> 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/portal-quick-setup/organizational-setup/manual-creation-import.md). # Manual Creation / Import {% @arcade/embed flowId="WsXD4L2Z5zy3Srlk9JWw" url="" %} ### Creating and maintaining your organisational structure Organisational data such as locations, employees, and groups can be created and maintained in different ways. The right approach depends mainly on the size of your organisation, the amount of data you need to manage, and how frequently that data changes. For smaller organisations or occasional updates, you can create and edit the information manually in equipme. This gives you full control and is often the quickest option when only a few entries are involved. When setting up multiple entries at once, you can import the data using an Excel file. This reduces manual work and helps ensure that information such as names and structures remains consistent. For larger organisations or data that changes regularly, an HR sync provides a more scalable solution. equipme connects to your source system and automatically keeps the relevant organisational data up to date. The following sections explain each of these options in more detail and show how they are used in practice. --- # 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/portal-quick-setup/organizational-setup/manual-creation-import.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.