# Sets

A set is a collection of objects you've arranged together, saved as a single library item. The kitchen table with plates, chairs, and scattered papers becomes "Coffee setup" – one drag into the next scene and the entire arrangement is back, intact.

## Watch

{% embed url="<https://www.youtube.com/watch?v=CtjZNzeJBW8>" %}

![Save Set modal open over a populator-style cluster of boxes in Build mode. The modal has a Name field defaulted to "Box 26", a Description field, and Cancel / Save buttons](/files/YM6253KTVqhjDpGV7mCb)

## What it does

Vignettes recur. A trash cluster on a city street corner; the props on a desk; a wedding-table arrangement; a kitchen-island layout. Building each one from scratch every time is busywork. Sets give you a one-action way to capture an arrangement and redeploy it.

A set preserves:

* Every object in the selection
* Their relative positions, rotations, and scales
* Each object's name, description, image reference, and LoRA
* Parent-child attachments within the set

A set does not preserve:

* Animation keyframes (those are shot-bound, not scene-bound; see [Animation and shot time](/overview/concepts/animation-and-shot-time.md))
* The scene's environment settings (sun, fog, terrain) – those are scene-level, not set-level

## How to save a set

{% stepper %}
{% step %}

#### Arrange the objects in the scene

Build the vignette as you'd want it everywhere. Spacing, rotations, parent attachments – everything authored now is what gets reused.
{% endstep %}

{% step %}

#### Marquee select the group

Click the marquee icon, drag a box around the objects you want in the set. Confirm the count in the contextual menu reflects the selection.
{% endstep %}

{% step %}

#### Open More Options → Save as Set

The contextual menu's three-dot icon opens secondary actions. Click **Save as Set**. A modal opens with **Name** and **Description** fields.
{% endstep %}

{% step %}

#### Name and describe the set

Use a descriptive name. "Coffee table arrangement", "Pirate ship deck props", "Trash corner cluster". The name is what you'll search for later in the Asset Library. Description is optional but helps you and teammates remember what's in the set.
{% endstep %}

{% step %}

#### Save

The set lands in the **Asset Library** (under **My Assets** or **Team Assets** depending on the active workspace), available across every project.
{% endstep %}
{% endstepper %}

## How to use a saved set

Open the asset library. Click the **My Assets** category (or **Team Assets** if it was saved at the team level). The set appears as a single thumbnail. Drag it into a new scene; the entire arrangement instantiates at the cursor's projected ground point.

Once placed, the set behaves like a parent group:

* Click any object inside the set to select it individually.
* Marquee or `Shift+click` from the [Scene Outliner](/build/scene-outliner.md) to select the whole set.
* Move the parent group to relocate the entire arrangement.

To break the set apart and treat the objects as independent: select the set, right-click → **Detach all children**. The arrangement stays where it is, but the parent grouping is removed.

## My Assets vs Team Assets

When saving, the set lands in whichever workspace is active when you save:

* **Personal workspace** → set goes to **My Assets**, visible only to you.
* **Team workspace** → set goes to **Team Assets**, visible to every team member.

Build a "Hero product, dressed" set in the team workspace and every team member can drop it into their own scenes without re-uploading the CAD or rebuilding the dressing. Saves real time on agency teams pitching the same brand across multiple campaigns.

## Limits and known issues

{% hint style="warning" %}
**Sets don't update across scenes after you save.** If you tweak the objects in one place, the set's stored version doesn't change. Re-save with the same name to update, or treat sets as immutable starting points.
{% endhint %}

* **Sets cap on object count.** Very large sets (hundreds of objects) take longer to drop in. For city-scale arrangements, use a [populator](/build/populators.md) instead.
* **Cross-team sets aren't supported.** A set saved in Team A's workspace doesn't appear in Team B's library. Re-save in each workspace where you need it, or move the source files via [Smart Import](/build/import-your-own-models.md).

## Related

* [Selection and grouping](/build/selection-and-grouping.md)
* [Asset library](/build/asset-library.md)
* [Working with objects](/build/working-with-objects.md)
* [Populators](/build/populators.md): for procedural-distribution use cases that sets don't fit.


---

# Agent Instructions: 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:

```
GET https://help.intangible.ai/build/sets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.