> ## Documentation Index
> Fetch the complete documentation index at: https://docs.holos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Objects

> Browse, upload, and manage 3D models for tracking and course content.

The **Objects** library is a shared repository of 3D models available to your organization. Global objects are shared across the platform; private objects are uploaded by your team. Objects marked as trackable can be used as reference targets during [Holos Capture](/capture/index) sessions.

## Browsing and searching

Objects can be viewed as tiles or a table. Search by name, provider, or tag. Paginated at 50 per page; use **Flagged** and **Archived** links in the bottom bar to switch views.

Each tile shows the object name and provider. The platform library includes thousands of CC0 objects from providers like Poly by Google alongside any org-private objects your team has uploaded.

## Object detail

Click any object to open its detail page. The top of the page shows:

* **Name** and **created by**
* **Description**: editable free-text field
* **License**: dropdown (e.g. None / All Rights Reserved, CC0)
* **Tags**: free-form labels for search and filtering

The stats panel in the top right shows:

| Field     | Description                                               |
| --------- | --------------------------------------------------------- |
| Triangles | Polygon count of the mesh                                 |
| Size      | File size                                                 |
| Trackable | Whether an AR reference descriptor exists for this object |

The full 3D viewer below lets you inspect the object from any angle.

### Actions

The icon row in the top right of the detail page provides:

* **Info**: object metadata
* **Flag**: report an issue with the object
* **Status**: approval state
* **Download**: download the object file; click to select format (GLB, USDZ, etc.)
* **Delete**: remove the object from your org

## Reporting issues

Click the flag icon to open the **Report issue** dialog. Select the issue category and click **Report**:

| Issue              | Description                                                |
| ------------------ | ---------------------------------------------------------- |
| Backfaced textures | Geometry normals are inverted                              |
| Large textures     | Texture resolution is excessive                            |
| Off origin         | Object pivot point is misplaced                            |
| Bad thumbnail      | Auto-generated thumbnail doesn't represent the object      |
| Bad orientation    | Object is rotated incorrectly relative to its expected use |
| Other              | Any other issue                                            |

## Uploading objects

<Note>Uploading objects requires admin or manager access.</Note>

Admins and managers can upload new org-private objects via the **Upload** button. Supported formats:

| Format | Notes                                          |
| ------ | ---------------------------------------------- |
| GLB    | Primary format, no conversion needed           |
| USDZ   | Retained for AR; GLB generated for web preview |
| OBJ    | Converted to GLB automatically                 |
| FBX    | Converted to GLB automatically                 |

## Object tracking

**Object tracking** lets Holos Capture recognize a specific real-world object and record its position throughout a session. Not all objects are trackable by default — trackable objects display a scan icon on their tile in the library, and the **Trackable** stat on the detail page shows **Yes** or **No**.

### Why it's necessary

A 3D model on its own is just geometry — the app has no way to spot the matching physical object in the room. To bridge that gap, the platform builds a **reference object**: a compact descriptor trained from the model that the Capture app matches against the live camera feed to find and follow the real thing.

Building a reference object is a compute-heavy job that runs on Holos infrastructure, so it isn't instant. You enable it once per object; afterwards the object is permanently trackable and ready to use in any capture.

<Note>
  You only need to enable tracking for objects you want the app to follow during a session. Models used purely as course content or for reference don't need it.
</Note>

### Enabling object tracking

1. Open the object from the library
2. Click the **scan** icon in the action row (top right of the detail page)
3. Choose your tracking settings (see below)
4. Click **Enable object tracking**

The **Trackable** stat reads **No** with tracking *queued* or *in progress* until the job completes, and a small dot on the scan icon indicates an active request. You can reopen the dialog any time to update the settings while the job is still queued.

Tracking is also requested automatically when you link an object to a [skill](/dashboard/skills) from the skill's **Tracked objects** section: if the object isn't yet trackable, the platform submits the request for you and shows a confirmation toast.

<Note>
  Reference objects are built by the Holos team's processing pipeline. Once the job finishes, the **Trackable** field flips to **Yes** and the object becomes available in Holos Capture.
</Note>

### Tracking settings

The settings you choose describe how the object is handled in the real world, which helps the pipeline build an accurate reference object.

**View mode** — how the object is approached during a session:

<CardGroup cols={3}>
  <Card>
    <img src="https://mintcdn.com/holosinc/M4HR1UgvFmLr_sUN/images/icons/view-front.svg?fit=max&auto=format&n=M4HR1UgvFmLr_sUN&q=85&s=ba93011e5e467e02ef7d889ee36b5998" alt="" width="28" height="28" noZoom data-path="images/icons/view-front.svg" />

    <p><strong>Front</strong></p>
    Viewed only from the front. Wall-mounted panels, controls, screens.
  </Card>

  <Card>
    <img src="https://mintcdn.com/holosinc/M4HR1UgvFmLr_sUN/images/icons/view-upright.svg?fit=max&auto=format&n=M4HR1UgvFmLr_sUN&q=85&s=ed5ebc8ee8c800e1eb5bbe2f0c18783b" alt="" width="28" height="28" noZoom data-path="images/icons/view-upright.svg" />

    <p><strong>Upright</strong></p>
    Stays upright, approached from any side. Benchtop equipment, freestanding machines.
  </Card>

  <Card>
    <img src="https://mintcdn.com/holosinc/M4HR1UgvFmLr_sUN/images/icons/view-all-angles.svg?fit=max&auto=format&n=M4HR1UgvFmLr_sUN&q=85&s=65066591d1ab24ed539b8f15487b7a1b" alt="" width="28" height="28" noZoom data-path="images/icons/view-all-angles.svg" />

    <p><strong>All angles</strong></p>
    Picked up and rotated freely. Handheld parts and tools.
  </Card>
</CardGroup>

<Note>
  **All angles** takes longer to train and carries a higher false-positive risk. Only choose it for objects that are genuinely handled from every direction.
</Note>

**Training mode** — how much compute the pipeline spends building the reference object:

| Mode         | Typical runtime | Best for                                       |
| ------------ | --------------- | ---------------------------------------------- |
| **Standard** | \~8 hours       | Most objects                                   |
| **Extended** | \~18 hours      | Small, handheld objects that need extra detail |

**Objects to avoid** — optionally pick look-alike objects from your library so the tracker doesn't confuse them with this one. Most useful when you have several visually similar models. Only objects that have a USDZ file can be selected.

Once an object is trackable, link it to a skill so it's prepared automatically when a session starts. See [Tracked objects](/capture/tracked-objects) for how linking and in-session tracking work.

## Approving uploads

Object approvals are handled in the [Object Approvals](https://app.holos.io/objects/approvals) queue. See [Object Approvals](/dashboard/organization#object-approvals) for the full review workflow.