> 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/what-an-asset-group-page-shows.md). # What an asset group page shows An asset group is a set of equipment of one type at a property, for example all the fire extinguishers or the sprinkler system, with each individual unit being an asset. You reach an asset group from the property's Asset Groups card. The header shows the group's type and an Active or Inactive status, with the property it sits on. The **Assets** tab lists the individual units and their details; you can switch between Table View and Card View and search them. Both views list every asset type set up for the group, including the ones you haven't added anything to yet — those sit at the bottom. Card View marks an empty type with "No assets of this type yet"; Table View shows it as an empty grid with no such text. Use the three-dot menu above the list to create an inspection report for the group when a report type is available. The same menu has **Download Assets as CSVs**. It downloads a ZIP file containing one CSV for each asset type currently shown in the list. Each CSV includes the Asset ID, the configured asset details, and the next due date for each applicable service. When you search the asset list, the download contains only those matching assets; clear the search first to download every asset in the group. On the right, the Recurring Services card holds the service schedules for this equipment, Automation Setup controls the outreach that goes out for it, and Next Automation shows what's coming up. Use Edit to rename or change the group. You can ask Essential what this group is, where it is, or how many units it has. **Timeline** is always at the bottom of the page, below the main content and side cards on every screen size. ![Asset group detail page](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-4caa5b3bdf8583463bc54a0197f54c4611180dcb%2Fasset-group-detail.png?alt=media) > **Where to find it:** Open an asset group from a property's Asset Groups card; the page header reads Asset Groups / ## Related guides * [Add or bulk-add assets to an asset group](/field-operations/assets/add-or-bulk-add-assets-to-an-asset-group.md) * [Create an inspection report from the office](/field-operations/inspection-reports/create-an-inspection-report-from-the-office.md) * [Asset groups and assets: terminology and screen labels](/field-operations/assets/assets-vs-asset-groups-vs-asset-items-the-terminology.md) * [Deleting an asset group (and what it removes)](/field-operations/assets/deleting-an-asset-group-and-what-it-removes.md) * [Recurring service templates and template groups](/field-operations/assets/recurring-service-templates-and-template-groups.md) * [See and browse all your asset groups (the Asset Groups page)](/field-operations/assets/see-and-browse-all-your-asset-groups-the-assets-page.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://learn.withessential.com/field-operations/assets/what-an-asset-group-page-shows.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.