# Organize assets with properties

URL: https://docs.glossi.io/set-up-the-product/properties

Define shared fields for your assets, choose where they apply, and learn when to use properties or tags.

A property is a field you create for your team to fill in on assets. For example, create a **Launch date** property once, then give each model its own launch date.

Creating a property and entering its value are two separate steps:

| Step              | Where                                                     | Example                                                            |
| ----------------- | --------------------------------------------------------- | ------------------------------------------------------------------ |
| Create the field  | **Add property** on an asset or **Settings → Properties** | Name it **Launch date** and choose the **Date** type.              |
| Fill in the field | **Properties** on an individual asset                     | Set one model’s Launch date to 12 March and another’s to 20 April. |

The **name** tells your team what the field means. The **type** controls what they can enter. The **value** is the answer for that particular asset. Creating a property does not fill in values automatically.

Properties work on **models, model variants, projects, templates, materials, props, renders, decals, backplates, and AI styles** in your workspace. They describe an asset; they do not change its appearance or Studio settings.

## Properties or tags?

Use **properties** when everyone should answer the same question about an asset. Use **tags** for flexible labels that do not need a dedicated field. An asset can use both wherever tags are available.

| Need                              | Use                            | Example                                 |
| --------------------------------- | ------------------------------ | --------------------------------------- |
| One consistent classification     | Single select property         | Season: Spring/Summer                   |
| Several values from a shared list | Multi-select property          | Markets: Europe, North America          |
| A reference, quantity, or date    | Text, Number, or Date property | Supplier reference, Weight, Launch date |
| A temporary grouping or reminder  | Tag                            | Website shortlist, Discuss at review    |

A property explains what a value means: **Season: Spring/Summer** identifies Spring/Summer as the asset’s season. Select properties also keep everyone using the same allowed options. Text, number, and date properties accept values of their respective types instead of an option list.

If you repeatedly add a family of tags such as `spring`, `summer`, and `winter`, make **Season** a property. Keep tags for labels that do not justify a field across the workspace.

## Choose a property type

### Single select: one choice from a shared list

Use this when an asset should have at most one answer, such as **Season** or **Product category**.

Create **Season**, choose **Single select**, and add options such as **Spring/Summer** and **Fall/Winter**. On each model, choose its season from that list. Choosing a different season replaces the previous choice. You can also leave the value empty.

Defining the options does not select one for every asset. It gives your team the same choices to use. Select types support filtering by their options in the Models and variant libraries.

### Multi-select: one or more choices from a shared list

Use this when several answers can apply to one asset, such as **Markets** or **Sales channels**.

Create **Markets**, choose **Multi-select**, and add **Europe**, **North America**, and **Asia**. One model might have Europe selected; another might have both Europe and North America.

A multi-select with one chosen value can look like a single select, but it allows another value to be added. Choose **Single select** when the field should enforce one answer; choose **Multi-select** when multiple answers are valid. Both can be left empty.

### Text: a value written separately for each asset

Use this for values that do not come from a fixed list, such as **Supplier reference** or **Internal note**.

Create **Supplier reference** and choose **Text**. There are no options to configure. On each model, enter its reference, such as **SUP-1042** or **SUP-2086**, then click away or press Enter to save.

Text values can contain up to 500 characters. Model search matches text property values. If everyone should choose from the same approved answers, use a select type instead.

### Number: a quantity or measurement

Use this for numeric values, such as &#x2A;*Weight (kg)** or &#x2A;*Unit cost (EUR)**. Include the unit or currency in the name so your team knows what the number represents.

Create &#x2A;*Weight (kg)** and choose **Number**. There are no options to configure. On one model, enter **1.25**; on another, enter **3**. Click away or press Enter to save. Enter the number itself, without a currency symbol or unit; zero and decimals are supported.

The field stores a number. It does not convert units or currencies. Number properties can currently be viewed and edited on assets, but the library UI does not yet offer numeric property filters or sorting by their values.

### Date: a calendar day or period

Use a name that explains what the date means, such as **Launch date**, **Review deadline**, or **License expiry**. A model can have several different date properties if your team needs them.

Create **Launch date** and choose **Date**. There is no list of dates to define. On each model, choose its launch date from the calendar and click **Save**. If 10 models launch on 10 different dates, create one Launch date property and enter a different value on each model.

For a period, create a property such as **Campaign period** and enable **Date range** before creating it. On an asset, enter the start date and an optional end date, then click **Save**. The end cannot be before the start. Date range settings are fixed when the property is created.

Dates contain calendar days only, without a time or time zone. A custom Launch date is separate from the asset’s automatically recorded creation or update date.

You can currently record and read these dates on assets. &#x2A;*The library UI does not yet support sorting by a custom date property or filtering it by a date period.** The existing Newest/Oldest sort uses the asset’s creation date, not its Launch date or another custom date.

## Define properties

Workspace owners and admins can create and manage properties. Members can set values on assets in their workspace.

From an asset, click **Add property** in its Properties section. Name the field, choose its type and add any choices. It defaults to that asset type; expand **Applies to** to include others. After creation, the new value field is focused on the same asset. The definition is shared across the workspace, but each asset has its own value.

Use **Settings → Properties** to manage all fields, including their order and archived definitions. Click a property row to edit it. Changes save automatically; Close finishes a pending name edit.

1. Click **New property** and enter a name.
2. Choose the type using the examples above. The type is fixed when the property is created.
3. Under **Applies to**, all asset types are selected by default. Deselect any that do not need this field. For example, Campaign could apply to projects, templates, and renders, while Supplier reference might apply only to models.
4. For select types, add at least one allowed option. Press Enter to add a choice, or paste a list with one choice per line. You can add more later.
5. Create the property, then open an asset to enter its value.

Edit an existing property to change its name or the asset types it applies to. Removing an asset type hides the field on those assets without deleting stored values; adding the type back makes them available again. Each asset has its own values: assigning Campaign to a project does not automatically assign it to that project's renders or models.

**Show on cards** is available for select types and displays values on model cards and supported library toolbars. At most two properties per asset type can use this setting. It does not add property badges or filters to every asset page.

### Curate options

Open a select property to change its options:

* **Rename** an option. Assets reference the option by ID, so they show its new name automatically.
* **Colour**: click the dot to choose or clear a colour.
* **Archive** an option to remove it from pickers. Existing values remain visible. Restore it from the Archived list.
* **Merge** one option into another when two mean the same thing. Every asset in your workspace carrying the first option moves to the second, and the first option is removed.

Option labels must be unique within a property.

### Order, archive, and restore

Use the up and down arrows on the Properties list to set the field order.

Archive a property you no longer use. It disappears from editors and filters, but its values remain stored. Restoring it brings those values back. A workspace can have up to 30 active properties, each with up to 200 options.

## Set values on an asset

Open the asset and find **Properties**:

| Asset                     | Where to edit                                                            |
| ------------------------- | ------------------------------------------------------------------------ |
| Model                     | The model detail page                                                    |
| Model variant             | The variant editor                                                       |
| Project                   | The Details panel or Project Details modal                               |
| Template                  | **Manage template → Organization** on a template owned by your workspace |
| Material                  | The material detail page, below Details                                  |
| Prop, decal, or backplate | The asset's inspector                                                    |
| Render                    | The **Details** popover                                                  |
| AI style                  | The style editor                                                         |

Only properties whose **Applies to** includes that asset type appear. If a field is missing, ask a workspace admin to update its settings. Shared catalogue assets must belong to your workspace before you can classify them with your workspace's properties.

* Select and multi-select rows open a picker and save when you choose a value.
* Text and number fields save when you click away or press Enter.
* Date fields use calendar days, without a time or time zone. Choose the date (and optional end date for a range), then click **Save**. The end cannot be before the start.
* Clear a value by deselecting its options or emptying the field. For a date range, clear both dates and click **Save**.

The model quick-look pane shows values for reference; use the model detail page to edit them.

### Set values in bulk

On the Models page, select models and choose **Set property** from the selection bar. The variant catalogue also supports bulk property editing. This currently supports **Single select** and **Multi-select** properties; edit Text, Number, and Date values on individual assets.

* Single select properties replace the existing value.
* Multi-select properties add the selected options to existing values.
* The clear button, named for the property (for example **Clear Season on all**), removes the value from every selected asset.

Other asset types currently use their individual property editors.

## Find models by property

The Models page's **Filter** menu lists select and multi-select properties, their options, and matching counts. Selecting Season: Spring/Summer and Markets: Europe finds models that match both fields. Selecting Europe and North America within Markets finds models with either market.

Model search also matches property text and option labels. Filters stay in the URL and can be kept as a saved view. The variant catalogue also supports property filters. The other asset types support storing and editing values; their list pages do not yet provide the same property filters, search, or card badges.

## Use properties from the API or an agent

> **Enterprise.** The API and agent access are available on Enterprise.

The REST API and MCP connector can list and manage property definitions, archive or restore them, update asset values, and find assets by their values. For example, ask an agent to “show all models with Season set to Spring.” Workspace admins manage definitions; members can edit values. See [Properties and asset search](https://docs.glossi.io/api/properties.md) for examples, all supported operations, and number/date filters available through the API.

## Related

* [Models](https://docs.glossi.io/library/models.md)
* [Create product variants](https://docs.glossi.io/set-up-the-product/variants.md)
* [Projects](https://docs.glossi.io/studio/projects.md)