> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/assets/assets-vs-asset-groups-vs-asset-items-the-terminology.md). # Asset groups and assets: terminology and screen labels An **asset group** is one tracked installation or set of equipment at a property. For example, the fire extinguishers at 123 Main Street can be one asset group. An **asset** is an individual unit or device inside that group. The asset group has a type, property, optional description, and Active or Inactive status. The assets inside it have their own attribute values such as size, make, model, or location. One Backflow asset group, for example, can contain several individual backflow assets. The current screen labels follow that same distinction. The main **Asset Groups** page and a property's **Asset Groups** card list asset groups. **Add Asset Group**, **Edit Asset Group**, and **Delete Asset Group** operate on a group. On an asset group page, the **Assets** tab and controls such as **Add Asset**, **Edit Asset**, and **Delete Asset** operate on individual assets. Before this terminology rollout, **Asset Groups** were labeled **Assets**, and **Assets** were labeled **Asset Items**. Older screenshots, exports, or saved instructions may still use those former labels. Use the grain of the record—not the legacy word alone—to identify what they mean. Recurring services and automations belong to the asset group. Its asset group type identifies the kind of installation or equipment set, the assets are the individual units or components, recurring services define inspection requirements and due dates, and automations define what Essential should do when service is coming due. > **Where to find it:** Open an asset group from a property's **Asset Groups** card or the main **Asset Groups** page. The page heading reads **Asset Groups / *****\[type name]***, and its individual assets appear on the **Assets** tab. ## Related guides * [What an asset group page shows](/field-operations/assets/what-an-asset-group-page-shows.md) * [Add or bulk-add assets to an asset group](/field-operations/assets/add-or-bulk-add-assets-to-an-asset-group.md) * [Deleting an asset group (and what it removes)](/field-operations/assets/deleting-an-asset-group-and-what-it-removes.md) * [Editing, reordering, and deleting assets](/field-operations/assets/editing-reordering-and-deleting-asset-items.md) * [Recurring service templates and template groups](/field-operations/assets/recurring-service-templates-and-template-groups.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 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://learn.withessential.com/field-operations/assets/assets-vs-asset-groups-vs-asset-items-the-terminology.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.