> 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/dokumentation/help/glossary.md). # Glossary Glossary: all important terms in equipme from A to Z. | Term | Meaning | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Cancellation** | Request type for terminating or canceling a service | | **Call-off** | Request type for delivering a service from the warehouse or from a pre-order | | **Department** | Group of the type "Department". Its managers approve with department head approval. | | **Add-on** | Additional service for a main service, e.g. warranty extension, setup, pickup | | **Offer** | Orderable variant of a service with price, term, billing and offer type. A service can have several offers; for own services, each offer has no or exactly one offline supplier | | **Offer type** | Purchase, rental, mobile contract or leasing | | **Requester** | The person who submits a request in the Marketplace | | **Change** | Request type for changes to an existing service (options, add-ons, replacement) | | **API key** | Key that other systems use to access equipme; has full administrator rights | | **Asset** | A specific, assigned instance of a service (also service instance) | | **Asset ID** | Unique identifier of an asset in equipme | | **Order processing** | Area where your own services are provisioned and completed internally | | **Automation** | Licensed module for workflows and integrations | | **Basic service** | Company-wide foundation (e.g. tenant) that other services depend on; once per company | | **Justification** | Text used to justify a request, approval or rejection | | **Observer** | Person who sees an approval request and may decide on it, e.g. a representative | | **Order request** | A requested item in the cart that is waiting for approval and ordering | | **Order authorization** | Release of a hosted customer by their provider to be allowed to order at all | | **Order** | Order sent to a supplier or to internal processing | | **Order number (PO)** | Your own reference number for an order | | **Business owner** | Role that manages the assigned services of an organizational unit | | **Custom links** | Your own links in the menu (standalone customers) | | **Equipme Operate** | equipme's ticket system for support requests and their handling → [Equipme Operate](/dokumentation/operate.md) | | **Purchaser** | Role that may place orders | | **Confirmation of receipt** | The recipient's confirmation that they have received a service | | **Forecast** | Expected costs including requested changes | | **Approval request** | Process by which order requests are submitted for approval | | **Approval notice** | A supplier's conditions that must be confirmed when ordering | | **Approval type** | Who approves with simple approval: supervisor, department head, location executive or cost center manager | | **Group** | Organizational unit: department, team, project, company or custom | | **Group (Equipme Operate)** | Team in the ticket system, e.g. 1st level; the tickets assigned to it form its queue → [Queues](/dokumentation/operate/queues.md) | | **Group role** | Role in a group: member, manager, deputy manager | | **Hosted customer** | Company that uses equipme via a provider | | **HR sync** | Automatic transfer of organizational data from the HR system | | **Internal** | Label for your own services in the Marketplace | | **Inventory** | List of all services or assets of the company | | **Inventory number** | Your own asset label, e.g. barcode or ERP number | | **Cost center** | Organizational unit to which costs are assigned; linked to a billing address | | **Lifecycle** | Overall state of a ticket in Equipme Operate: Open, Resolved or Closed; each status is mapped to a lifecycle → [Work items](/dokumentation/operate/work-items.md) | | **Warehouse** | Location where services wait to be used; also as a supplier warehouse | | **Term extension** | Automatic extension of a contract after the term ends | | **Marketplace** | Catalog of all orderable services; "My Marketplace" shows the offers you may request for yourself | | **Feature** | Property of a service or asset, e.g. serial number, color, storage | | **Offline supplier** | Supplier that does not use equipme itself and is maintained manually | | **Option / variant** | Configurable property of a service with selectable values | | **Planner** | Role that may prepare but not order | | **Platform supplier** | Supplier that uses equipme itself and is connected to the company | | **Provider** | Vendor through which a hosted customer uses equipme and obtains services | | **Queue** | A group's backlog in Equipme Operate: all tickets assigned to the group → [Queues](/dokumentation/operate/queues.md) | | **Invoice issuer** | Who invoices a service, if different from the supplier | | **Self-service** | Personal "My workspace" section where employees see their equipment and request new items | | **Self-service tag** | Keyword that controls which offers an employee sees in self-service | | **Service** | Anything that can be assigned and ordered: hardware, software, cloud, services | | **Service owner** | Organizational unit responsible for specific services | | **Service portfolio** | Your own internal offering of services | | **Single sign-on (SSO)** | Sign-in with the company account, e.g. Microsoft | | **Standalone customer** | Company with its own equipme license | | **Location executive** | "Location manager (purchaser)": may order and approve for their locations | | **Representative** | Stand-in for an employee, e.g. for approvals | | **Support request** | An employee's request to support, which creates a ticket → [Support requests and tickets](/dokumentation/self-service/tickets.md) | | **Theme** | Appearance of the app (colors, logos) | | **Ticket** | Case in Equipme Operate with a conversation, status and responsibility → [Support requests and tickets](/dokumentation/self-service/tickets.md) | | **Ticket contact** | Person for whom tickets are submitted in Equipme Operate; created automatically for employees | | **Linked service** | Service that is requested and approved together with a main service | | **Pre-order** | Order without a fixed recipient for a later call-off | | **Supervisor** | An employee's direct manager | | **Template** | Package of several services. Two separate kinds: templates from template management are assigned in the Marketplace; onboarding templates at a location or group are assigned automatically to new employees there | | **Further information** | Custom additional fields on locations, employees and groups | | **Workflow / flow** | Automated process in the automation module | --- # 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/dokumentation/help/glossary.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.