> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/organizations/server-labels.md).

# Server labels

Go to a server's **Labels** tab. Label a server with anything you want to group it by — a game, an environment, a team, a cost centre — then search the [server list](/organizations/servers-page.md) by a label's value to find every server carrying it. This is how you build your own groupings, independently of your [organizational structure](/organizations/organizational-units.md).

## Adding a label

{% stepper %}
{% step %}

#### Open the Labels tab

Open the server from the [Servers page](/organizations/servers-page.md) and choose **Labels**.
{% endstep %}

{% step %}

#### Add a label

Click **Add label** in the **Your labels** card.
{% endstep %}

{% step %}

#### Enter a key and a value

The **key** is the category (`environment`, `game`, `team`); the **value** is this server's entry in it (`production`, `my-game`, `platform`).
{% endstep %}

{% step %}

#### Save

The label appears in **Your labels** straight away.
{% endstep %}
{% endstepper %}

## Changing and removing a label

In **Your labels**, click a label's **value** to edit it in place. To remove one entirely, use **Delete label** on its row.

If you add a label with a key that already exists on the server, the dialog says so and the button changes to **Replace label** — so you replace the existing value rather than creating a second entry for the same key.

## The rules

| Rule              | Limit                                                                 |
| ----------------- | --------------------------------------------------------------------- |
| Labels per server | **50** that you create                                                |
| Key length        | Up to **50** characters                                               |
| Value length      | Up to **150** characters                                              |
| New key format    | Lowercase letters, digits, `-` and `_`. Must start with a **letter**. |
| Value             | Anything except the literal word `null`                               |

The card header counts what you've used (*12 of 50*). At the limit you can still change and delete the labels already there, but not add another.

A handful of keys are reserved for the i3D.net platform and can't be used for your own labels: `application_build_id`, `application_id`, `dc_location_id`, `fleet_id`, `host_id`, `region_id` and `region_name`.

{% hint style="info" %}
Keys are matched case-insensitively, so `Environment` and `environment` are the same key. The key is displayed the way you typed it.
{% endhint %}

## Set automatically

Below your own labels, a **Set automatically** card shows labels i3D.net maintains — they record where the server sits in our platform and are kept up to date for you. They're read-only, they **don't count towards your 50-label limit**, and a server-list search never matches them.

Where a server isn't reserved for a fleet, `fleet_id` and `region_id` read *Currently not reserved for a fleet*.

## Finding servers by label

On the [Servers page](/organizations/servers-page.md), search for a label's **value**. Servers that match on a label show the matching label as a chip beneath the server name, with the matched text in bold — so you can see why each row is in the results. Up to two chips show per row, then *+N more*.

{% hint style="info" %}
Search matches label **values**, not keys. To find every production server, search for `production`, not `environment`.
{% endhint %}

## Labels and the API

Labels are part of the i3D.net API, so you can keep them in step with your own tooling rather than setting them by hand. See the [Host Label API](https://docs.i3d.net/game-hosting/elements/application/label) documentation.

## Related topics

* [Server details](/organizations/server-details.md)
* [The Servers page](/organizations/servers-page.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.i3d.net/organizations/server-labels.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.