> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/references/references-classic/glossary-classic/object-classic.md).

# Object (classic)

An *object* is a representation of an identifiable element in your IT infrastructure whose properties, activities and generated events are monitored by Nexthink. An object can refer either to a hardware or to a software element.

There are ten types of objects in Nexthink. The availability of each type of object and the information that they carry depend on the platform of the end-user devices that originated them. Object types that are available for multiple platforms can be divided into *specific* to a platform and *shared* by platforms. Objects which are specific to a platform belong to one platform only. For instance, devices are platform specific because one device may be either a Windows device, a Mac OS device, or a Mobile device. On the other hand, users are platform shared, because the same user may have been seen in Windows, Mac OS, or Mobile.

| Available for platforms    | Object type                                                                                    | Platform specificity |
| -------------------------- | ---------------------------------------------------------------------------------------------- | -------------------- |
| Windows \| macOS \| Mobile | [User](/platform/references/references-classic/glossary-classic/user-classic.md)               | Shared               |
| Windows \| macOS \| Mobile | [Device](/platform/references/references-classic/glossary-classic/device-classic.md)           | Specific             |
| Windows \| macOS           | [Package](/platform/references/references-classic/glossary-classic/package-classic.md)         | Specific             |
| Windows \| macOS           | [Application](/platform/references/references-classic/glossary-classic/application-classic.md) | Specific             |
| Windows \| macOS           | [Executable](/platform/references/references-classic/glossary-classic/executable-classic.md)   | Specific             |
| Windows \| macOS           | [Binary](/platform/references/references-classic/glossary-classic/binary-classic.md)           | Specific             |
| Windows \| macOS           | [Port](/platform/references/references-classic/glossary-classic/port-classic.md)               | Shared               |
| Windows \| macOS           | [Destination](/platform/references/references-classic/glossary-classic/destination-classic.md) | Shared               |
| Windows                    | [Domain](/platform/references/references-classic/glossary-classic/domain-classic.md)           | Shared               |

***

RELATED CONCEPTS

* [Activity](/platform/references/references-classic/glossary-classic/activity-classic.md)
* [Event](/platform/references/references-classic/glossary-classic/event-classic.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://docs.nexthink.com/platform/references/references-classic/glossary-classic/object-classic.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.