<!-- https://nuforce360.com/help/service-manager/field-assets -->
# Field Assets

Help-centre article on the Field Assets screen for tracking field equipment and mobile assets in Service Manager.

# Field Assets

Use this screen to keep track of your business's field equipment and mobile assets in one place. Each asset is listed with its current status, so you can see at a glance what is active, sitting idle, or in for maintenance.

## What you can do here

- Browse your field assets in a list, with paging if you have more than fit on one screen.
- See, for each asset, its name, status (shown as Active, Inactive, or Maintenance), type, serial number (labeled SN:), location, and a short description.
- Add a new field asset to the list.
- Edit an existing asset's details.
- Delete an asset you no longer need to track. You are asked to confirm before anything is removed, since deleting cannot be undone.

## Steps: add a field asset

1. From the Field Assets screen, use the add (new) action to start a new entry.
2. Fill in the asset's details: name, type, serial number, location, and status.
3. Save the entry. It appears in your Field Assets list.
4. To make changes later, open the asset's edit action, update the details, and save again.
5. To remove an asset, choose delete on its row and confirm in the dialog that appears.

## Related

- [Assignments](/help/service-manager/assignments)
- [Service Packages](/help/service-manager/services)

<!-- REVIEW NOTES (drafting agent could not verify):
  1. The route's page.tsx currently binds this screen to the backend model name 'business.user' (the staff/team-member model) rather than a dedicated field-asset model, and no backend $browser configuration for asset-specific columns/actions was found in the API repo. This suggests the screen may still be a work-in-progress stub, so real production behaviour (exact table columns on desktop, which toolbar/add button appears, and the create/edit form's actual fields) is backend-declared at runtime and could not be confirmed from the frontend code alone.
  2. The specific asset fields (name, status, type, serial number, location, description) and the edit/delete row actions are confirmed from the FieldAssetCard component, which per the code is used for the card layout (always on mobile, and on desktop only if a page opts into cards; this page explicitly opts into a table on desktop via desktopRenderAs='table'). Whether the desktop table shows exactly the same fields was not confirmed.
  3. Whether a search box, filters, or a visible 'add new' toolbar button actually render on this screen depends on data the backend browse endpoint returns for the bound model, which was not available to inspect; the article describes adding an asset in general terms rather than naming a specific button label.
  4. The two Related links assume a /help/service-manager/... URL convention mirroring the app's own route paths; the actual help-center path scheme was not verified.
-->