# Assign attributes

<div class="ng-access" markdown>
**Who can do this:** <span class="ng-badge ng-badge--superuser">Superuser</span> <span class="ng-badge ng-badge--admin">Admin</span> &nbsp;·&nbsp; **Where:** Dashboard → Administration → **Assign Attributes**
</div>

This page decides which data fields appear on equipment forms: attach attributes to an **equipment type** (every unit of that type gets them) or to a **subtype** (only that subtype gets them), and mark which are required.

<!-- SCREENSHOT: assign-attributes-01.png — context selector, unassigned attribute picker, and existing assignments -->

## Pick the context

1. Choose **Assign attributes to:** *Equipment Type* or *Subtype (Per Equipment Type)*.
2. Select the **Equipment Type** — and, in subtype context, the **Subtype**.
3. Use **Search Assignments** to filter the existing list if it's long.

## Assign attributes

1. In **Unassigned Attributes**, filter the list with the *Filter attributes…* box and select one or more entries (the list is multi-select).
2. Optionally tick **Mark selected as required** — required attributes must be filled when equipment is saved.
3. Select **Assign Selected**. The attributes move into **Existing Assignments** immediately.

## Manage existing assignments

- Toggle **Required** per attribute directly in the list — it saves instantly.
- Remove a single attribute from the current selection; you'll be asked to confirm (*"Remove this attribute from the current selection?"*).
- The **Danger Zone**'s **Remove All** strips every assignment from the current type/subtype at once, after confirming *"Remove ALL assignments for the current selection?"* — useful when rebuilding a type's schema, dangerous otherwise.

!!! note "Removing an assignment doesn't delete data"
    Unassigning an attribute stops it appearing on forms for that type — values already recorded on equipment are not erased, and reassigning the attribute brings them back into view.

## Related articles

- [Manage equipment subtypes](manage-subtypes.md)
- [Set client field order](client-field-order.md) — per-client ordering of these attributes