> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/your-organization/units.md). # Units A Unit represents a physical location where your employees work — a store, hotel, restaurant, warehouse, or office, or any other site. ## Why set up Units? * **Organize teams by location** — each team belongs to a unit * **Schedule Missions to locations** — Missions target specific units * **Automatic time zones** — set automatically based on the unit's address * **Ticket routing** — each unit gets its own [Ticket Board](/your-organization/ticket-boards.md#unit-ticket-boards) automatically ## How to create a Unit 1. Go to **Units → New Unit** 2. Enter the unit name and physical address (state, county, city) 3. The time zone is set automatically 4. Save After creating a unit: * You can add [**Teams** ](/your-organization/teams.md)to the unit * You can assign [**People** ](/your-organization/people.md)to the unit {% embed url="" %} ## Unit hierarchy Units can contain sub-levels to mirror your real-world structure: ``` Organization └── Unit (Location) e.g. "Downtown Hotel" ├── Building e.g. "Tower A" │ └── Area e.g. "Lobby Floor" └── Building e.g. "Tower B" ``` Buildings and Areas are optional — use them only for large locations. ## Good to know * The physical address determines the **time zone** for all scheduling and reporting * Each unit automatically gets a [**Unit Ticket Board**](/your-organization/ticket-boards.md#unit-ticket-boards) — no extra setup needed --- # 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, and the optional `goal` query parameter: ``` GET https://documentation.taskmaverick.com/your-organization/units.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.