> For the complete documentation index, see [llms.txt](https://help.allwage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.allwage.com/fundamentals/users-and-employees/teams.md). # Teams Group employees by department, shift, or location A team is a way to **group employees together** — by department (like "Head Office", "Workshop", or "Packing"), by location, or by shift. How you group them depends on how your company is structured. Each employee is assigned to **one team**. You can see the team assignment in the **Team** column on the [employee list](/fundamentals/users-and-employees/employees.md), and you can view and manage your teams under **Manage > Teams** in the portal. ## Why Teams Matter Teams aren't just labels — they affect how you use AllWage in three important ways: 1. **Reporting** — when you run reports, you can filter by team. Instead of scrolling through every employee in the company, you can pull up just one team and see their clocking data, attendance, or hours worked. 2. **Management** — you can view and manage employees by team, for example when reviewing attendance or making bulk changes. This keeps things organised and avoids information overload. 3. **Configuration** — employees in different teams often have different operational setups. For example, a "Warehouse" team might start at 6:00 AM while "Head Office" starts at 8:00 AM. Clock templates and working hour patterns are assigned directly to employees — one by one or in bulk — giving you flexibility in how each team operates. ## Managing Teams Teams are usually configured during your initial setup, but they can be updated at any time as your company structure changes — for example, when you add a new department or merge two teams. * **View and edit teams:** navigate to **Manage > Teams**. * **Move employees between teams:** open an employee from the [employee list](/fundamentals/users-and-employees/employees.md) and change their team, or select multiple employees and use the **Move to team** [bulk action](/fundamentals/users-and-employees/employees.md#bulk-actions). --- # 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://help.allwage.com/fundamentals/users-and-employees/teams.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.