> 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/offer-management/template-management.md). # Template management Create and maintain Marketplace templates (equipment packages); difference to onboarding templates that locations and groups assign automatically. **Path:** sidebar → **"Offer management" → "Template management"** Templates bundle several services into a package, e.g. "Standard workplace" or "Field service equipment". equipme has **two separate kinds** of templates. They are built the same way (services with offer and options), but are created in different places and used differently: | | **Marketplace template** | **Onboarding template** (automatic assignment) | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | Where created | Here in **"Template management"** | Directly at the [location](/dokumentation/organization/locations.md#template-tab) or [group](/dokumentation/organization/groups.md), **"Template"** tab | | How many | as many as you like | at most one per location or group | | How used | Someone selects it in the Marketplace and **assigns it deliberately** (see [Templates in the Marketplace](/dokumentation/procurement/marketplace/ordering-templates.md)) | **Automatically**: whoever is assigned to the location or group receives the services as a request | | "Template type" | "Employee", "Location", "Cloud" and others (see below) | "Location - Automatic assignment" or "Group - Automatic assignment" | | Visible in the Marketplace | yes | no | | Visible in this list | yes | no | **A template always serves one purpose only.** A Marketplace template cannot be attached to a location or group, and an onboarding template appears neither here nor in the Marketplace. If the same services should be available both ways, maintain them in both templates. Both kinds go through the regular [approval process](/dokumentation/procurement/approval-settings.md) before ordering. ## The template list Columns: "Name", "Description", "Type", "Services" (number), "Monthly costs", "One-time costs", "Active". Buttons: **"New"**, **"Delete"**, **"Copy"**. ## Creating a template 1. Click **"New"**. 2. Choose the **"Type"**. It determines to whom the template can be assigned in the Marketplace: "Employee" (default), "Location", "Cloud" and, if your company uses a workplace service, "Employee with …". 3. Set the **"Name"** (required), "Description" and the **"Active"** status. 4. Save and add services on the detail page. Here you only create Marketplace templates. You create onboarding templates for automatic assignment directly at the location or group in the "Template" tab. ## The template detail page * **"Actions"**: "Edit", "Copy", "Remove". * Costs of the template ("Monthly", "One-time"). * **"Display service images on the marketplace"**. * **"Use free inventory first"**: existing warehouse stock is used before placing a new order. As long as this option is active, no linked services can be assigned. | Tab | Content | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **"Services"** | The included services with their configuration (offer, options); order via drag & drop or alphabetically | | **"Groups"** | Which groups the template is intended for. Users who only see the data of certain groups then find the template in the Marketplace. Members of the group do **not receive anything automatically** this way; that is what the group's onboarding template is for. | ## Keeping templates up to date If a service or an option is removed from the offering, the template shows "The template contains products or options that are no longer offered." At the location or group, the status "Template invalid" appears. Replace the affected service. --- # 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/offer-management/template-management.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.