> 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/groups.md). # Groups {% @arcade/embed url="" flowId="fiGlAnuS5YZQiiJpCrm9" %} Groups are a second dimension, not a place where equipment lives. A device is always assigned to an employee or to a warehouse. A group can hold a reservation on top of that. That is what makes them useful for planning. You can put 100 devices into stock and reserve ten for the apprentices starting in September and twenty for a site opening later, so nobody else takes them in the meantime. Departments are the obvious case, but they are not the interesting one. Project teams, regional teams, field sales, working students, external consultants: anything you would otherwise handle person by person is a candidate. Some groups come from your HR system, the rest you create yourself. ### Category and Tags These two fields look similar in the form and do entirely different jobs. **Category** is for your own overview. It bundles groups into larger blocks, so Marketing, HR and Finance can sit under Corporate Functions while IT and Development sit under Technology. With five groups you will not miss it. With fifty, it is the difference between a structure and a list. **Tags** reach beyond this screen. They decide what a group sees in the marketplace. Tag a service, give the same tag to the group, and the service appears for them and nobody else. Design software stays with the design team, premium phones with field sales, and you do not need a second catalogue for it. The same mechanism works on a single person, which is covered in [Self-service tags](/classes/admin/employees/self-service-tags.md). So a tag is worth planning, a category is worth keeping tidy. If you are unsure whether something belongs in either field, ask whether it should change what people can order. If yes, it is a tag. ### Naming and membership Give each group a name that explains itself and use the description field. It feels unnecessary with four groups and saves you a lot of guessing at forty, when nobody remembers who is supposed to be in "Team Süd 2". Memberships only help while they are current. When someone changes department, joins a project or moves into another role, the group is what carries their services and reservations with them. A group can also hold a template, so its members receive a standard set without anyone assigning it individually. And it can have a manager, who sees the members and the resources reserved for the group. That is a practical way to hand responsibility to someone who is not tied to a single site. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/MPzQpwcw4jRhiLwJF8e2" %} [Groups](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/groups) {% endcontent-ref %} {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/U8pfUbRiPnd0bRirROuy" %} [Automated Service Assignment with Templates](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/groups/automated-service-assignment-with-templates) {% endcontent-ref %} {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/1ADvCRH3JrRJGUukC8vo" %} [Preparing Devices for Later Delivery](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/assets/warehouse-management/preparing-devices-for-later-delivery) {% endcontent-ref %} ### Next Structure is done. Now build what people can request: [Offer management](/classes/admin/offer-management.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/groups.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.