> 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/mobile/manage-asset-groups-and-recurring-services.md). # Manage asset groups and recurring services on mobile Create or delete an asset group from a visit without starting an inspection report. You can also add or edit the group's recurring services. > **Where to find it:** Technician app → Visits → open an assigned visit → Visit Details → Asset Groups ## Before you start You need an internet connection and the matching role permission (if the app is still syncing changes you made offline, wait a moment and try again): **Create Asset Groups**, **Delete Asset Groups**, or **Manage Recurring Services**. Technician and back-office roles have all three by default. An administrator can turn any of them off for a role in **Settings → Roles & Permissions → Asset Groups**. ## Add an asset group 1. Tap **Add** to the right of **Asset Groups**. 2. Choose the **Asset Group Type** and enter an optional **Description**. 3. Tap **Save**. The group appears on the property's visits without creating an inspection report. 4. Open the group to add individual assets (**Assets** tab) or recurring services (**Services** tab). See [Add, edit, or delete an asset on mobile](/field-operations/mobile/add-edit-or-delete-an-asset.md). Creating another group of a type already on the property also requires **Create Multiple Asset Groups**. New groups created here start without recurring services; add services separately if you have permission. ### Manufacture and installation dates When adding or editing an asset, enter its actual manufacture or installation date in the matching date field. The date picker supports dates back to 1900, including equipment manufactured before 2000. Tap **Submit** to save the asset. ### Asset locations If the asset type has a GPS location attribute, adding an asset from the **Assets** tab tags the phone's current location automatically as soon as you choose the asset's **Type**. The **GPS** section is last in the asset form: a small map with **Move Pin** (drag the map under the pin, then tap **Done**) and, when editing, **Clear** — or **Not set** with **Use My Location** and **Place Pin** (put the pin on a map yourself). The change is saved when you tap **Submit**. Each asset card shows the location as a teal pin with its accuracy; tap it to open the group's map on that asset. The **Map** button at the top right of the group screen (beside the **⋮** menu, which shows only when your role can delete asset groups) opens the same full-screen map with every located asset — tap a pin, then its card, to open the asset. (The group's tabs are **Assets**, **Services**, and **Files**; the map is not a tab in the mobile app.) See [Tag where an asset is (GPS location attributes)](/field-operations/assets/tag-asset-locations-gps-attributes.md). ## Add or edit recurring services 1. Open an asset group from **Visit Details**. 2. Open the **Services** tab, then tap **Add** to the right of the tabs, or tap **Edit** on an existing service. 3. Choose the **Service**, **Frequency**, and **Frequency Unit**. Set the recurrence, rounding, and flexible timing as applicable. Available recurrence choices follow your company's settings. 4. For a new service, enter the last service or installation date, or the last due date for a schedule based on due dates. When editing, leaving the date unchanged preserves the recorded service history. 5. Tap **Save**. Edits preserve the service's existing asset filters and automation setup. New services use the group's existing automation type, or no automation when the group has no services. Saving recalculates the schedule using the same behavior as the web app; it can change when automated outreach or tasks are due. ## Delete an asset group 1. Open the group, tap the **⋮** menu at the top right, then tap **Delete Asset Group**. 2. Review the confirmation and enter a **Reason for deletion**. 3. Tap **Delete**. You return to Visit Details and the group disappears from the list. Deletion applies to the whole group, including its assets and recurring services. Existing inspection reports and started automation history are retained. See [what deletion removes](/field-operations/assets/deleting-an-asset-group-and-what-it-removes.md). If the office changed a recurring service while you had it open for editing, the save is refused with a message saying so. Pull down on the visit to refresh it, then make your change again on the current values. If the office deactivates or deletes the asset group just as you save one of its recurring services, your change is still saved, but the group leaves Visit Details and the app tells you the office has since removed it. ## What the office sees Every change you make here is recorded on the job's timeline under your name — for example *Asset group Fire Alarm "Lobby" added from the visit* or *Recurring service Annual Inspection (Annual) updated on Fire Alarm from the visit* — so the office can see what changed from the visit on the job page, alongside the asset group's own history. The job's task in the Tasks inbox (Tasks → Jobs) also gets an **Asset Group Changes** section: a one-line count of what changed from the visit — asset groups added or deleted, assets added or removed, attributes updated, recurring services added or updated (for example *1 asset group added · 37 attributes updated · 1 recurring service updated*). Assets you add, edit, or remove from Visit Details count here too, and so do the assets an inspection report submission adds, updates, or removes; attribute edits are counted per attribute, not per save, adding or removing an attribute photo counts as one, and a recurring service you edit more than once counts once. **View details** opens the changes grouped by asset group, each group linked to its page, with asset edits rolled up into one line per group (for example *120 attributes updated on 12 assets*). The section only appears once someone has changed something from a visit. --- # 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/mobile/manage-asset-groups-and-recurring-services.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.