> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infraon-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infraon-help/infinity-user-guide/asset/asset-categories-sub-categories/category-template.md). # Category Template The **Category Template** allows IT admins to predefine metadata fields, default behaviours, and automation logic for various asset categories. It acts as a blueprint that ensures asset records are consistent, enriched with required fields, and easily mapped during asset onboarding or discovery. It is used to: * Apply default settings like location, ownership, and asset ID. * Choose which field groups (like Procurement or OS details) should appear when creating assets. * Simplify asset management through structured, pre-configured templates. The template configuration is split into two tabs: 1. **Basic Details** 2. **Fields** ## **Basic Details** This section allows administrators to configure behavior-based options for the asset category.


Label	Action	Description / Example
Notify End Users on Asset Allocation	Click the toggle to enable	Sends a notification to the end user when an asset is allocated. User can Accept/Deny the asset.
Notify End Users on Asset De-allocation	Click the toggle to enable	Sends a notification to the end user when the asset is de-allocated.
Customize Asset ID	Click the toggle to enable	Allows customization of asset IDs as per customer-defined formats. Helps ensure traceability and compliance with internal tagging rules. Example: `#ESOL-D-0038`. Note: Common categories must include the "Customized Asset Id" field for this to work.
Select default asset location	Select from the dropdown list	Automatically assigns a default location when an asset of this category is created or discovered. Example: `Head Office – Bengaluru`.
Select default asset Owner/Technician	Select user(s) from dropdown	Assigns a default owner or technician to assets created under this category.

{% hint style="success" %} Once added, click on Next. {% endhint %} ## **Fields** This tab allows you to define **which metadata sections should appear** when assets of this category are created or imported.

These fields correspond to the ones described under [Asset Categories & Sub-Categories](https://docs.infraon.io/infraon-help/infinity-user-guide/asset/asset-categories-sub-categories) and are grouped as follows: * **Common Properties** (e.g., Hostname, IP, Serial Number) * **Cost Properties** (e.g., Book Value, Estimated Cost) * **Procurement Properties** (e.g., Warranty, AMC details) * **Assignment** (e.g., Owner, Requester, Allocation details) * **OS Properties** (e.g., OS Name, Product Key, Version) Admins can: * Select or deselect which sections to include in the template. * View or modify the fields inside each group by clicking **Show Fields**. * Create **Custom Fields** to accommodate organization-specific needs. {% hint style="info" %} * Once a template is configured, it automatically applies when creating assets under that category. * Multiple templates can be created to match the structure of workstations, servers, SaaS tools, or custom asset types. * Custom fields are fully supported for CSV imports and asset discovery. {% endhint %} --- # 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://docs.infraon.io/infraon-help/infinity-user-guide/asset/asset-categories-sub-categories/category-template.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.