> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/what-is-object-management.md).

# What is Object Management?

**Object Management** lets you register and manage customer assets in OutSmart.

Examples include boilers, HVAC units, installations, machines, and other serviced equipment.

### What Object Management helps you do

* register equipment per customer or location
* link objects to work orders and forms
* track service history, maintenance, and warranty dates
* organize equipment with templates, parts, and parent-child structures

### When to use it

Use Object Management when:

* you service the same equipment more than once
* technicians need context on site
* you want a clear asset history per customer
* you plan work around installed equipment

### How it fits in OutSmart

Objects work across multiple parts of OutSmart.

You can create them in the BackOffice.

You can also add or view them from work orders and the mobile app.

### Frequently asked questions

<details>

<summary>Is an object the same as a customer?</summary>

No.

A customer is the relation.

An object is the equipment or asset linked to that relation.

</details>

<details>

<summary>Can one customer have multiple objects?</summary>

Yes.

You can register multiple objects for the same customer or address.

</details>

<details>

<summary>Do technicians see objects in the app?</summary>

Yes, if the feature and the right app settings are available.

</details>

### Related topics

* [**Object Management**](/marketplace-packages-and-power-ups/power-ups/object-management.md)
* [**OutSmart packages**](/marketplace-packages-and-power-ups/marketplace/outsmart-packages.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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/what-is-object-management.md?ask=<question>&goal=<endgoal>
```

`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.