> 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/servers-page.md). # The Servers page Go to **Services → Servers**. The Servers page lists the servers your current organization can see. Which servers appear depends entirely on the organization you're working in and on the **Organization** filter. ## The toolbar | Control | What it does | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | **Search** | Filters as you type, across server name, IP address, host ID, service tag and [labels](/organizations/server-labels.md) — see below. | | **Server Type** | *All types*, Bare Metal, FlexMetal or Virtual. | | **Organization** | Chooses which organization's servers to show — see below. | | **Reset filters** | Appears once any filter is applied; clears search, type, organization, sorting and paging. | | **Columns** | Show or hide columns. | | **Density** | Compact, standard or comfortable row height. | ## Searching Search matches a server's **name**, **IP address**, **host ID**, **service tag**, and any [label](/organizations/server-labels.md) you've set on it. Type at least two characters — below that nothing is filtered and the full list stays on screen. When a server matches because of a *label* rather than something already visible in a column, the matching label appears as a chip beneath the server's name, with the matched part in bold. Up to two chips show per row, then *+N more*. This is why a row you didn't expect can appear in the results: the chip is the explanation. {% hint style="info" %} **Search terms have a maximum length.** A very long term can't be searched, and the Console says so on the row-count line beneath the table — *"This term is too long to search, so every server is shown"* — with the search box outlined in red. Shorten the term to filter again. {% endhint %} ## The Organization dropdown This is the control that decides your scope. It lists every organization and organizational unit in your current structure, plus one extra option separated at the bottom: * **Your current organization** (the default) — servers owned directly by the organization you're working in. * **Any organizational unit by name** — servers owned by that unit. * **All organizational units** — everything: your current organization *and* every unit beneath it. Use this for the full picture. Your choice is kept in the page address, so you can bookmark or share a particular view. ## The table | Column | Notes | | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Status** | A coloured dot. Hover it for the status in words — *Online*, *Offline*, *Check failed* or *Unconfirmed* — and for when that reading was last taken. *Unconfirmed* means the power state couldn't be determined, not that the server is down. | | **Name** | The server's name. Click it to open the server's details. | | **Server IP** | The one address you reach the server on, plus a count of the rest. A **Management** chip marks an out-of-band address and **Private** one reachable only from your own network. If your search matched a *different* address, that address is listed too with the match highlighted. | | **Location** | Data-centre location with a country flag. | | **Type** | Bare Metal, FlexMetal or Virtual. | | **Organization** | Which organization or organizational unit owns the server. | | **Billing Account** | The account number (K-number) the server belongs to — including for servers that came in through an [import](/organizations/importing-an-organization.md). | | **Billing** | How the server is billed — *Part of your agreement*, *No monthly charge*, *Billed through FlexMetal*, or an individual price. Hidden by default. | | **Chassis**, **Service Tag**, **Host ID**, **Category**, **Operating System** | Hidden by default; switch them on with **Columns**. | **Order Servers** at the top right of the page opens a short menu for ordering Bare Metal or FlexMetal servers. Click a row to open that server's [details](/organizations/server-details.md). Sort by clicking a heading (Location, Type, Chassis and Host ID are sortable). Page size options are 10, 25, 50 and 100. ## When the list is empty Which message you get says what emptied the list. **Your organization has no servers to show** * **"No servers in this organization"** — this organization has no servers of its own, but its organizational units do. Click **Show servers in all organizational units** to see them. * **"Need compute power?"** — there are no servers anywhere in your organization yet, with links to order [Bare Metal](/compute/api.md) or [FlexMetal](/compute/flexmetal.md) servers. **Your filters emptied the list** * **"No servers match *****\*****"** — the search ran and nothing matched. The message also reminds you that you can search by IP, host ID, service tag or label. * **"No servers in this view"** — an organization or server-type choice left nothing to show. Change either above, or use **Reset filters** to see every server. **The organization in the address can't be used** * **"Organization not found"** — no organization with that identifier exists. * **"No access to this organization"** — it exists, but it isn't one you can see. * **"Invalid organization address"** — the address doesn't name an organization in a form the Console recognises, usually a truncated or hand-edited link. Each of the three carries a link back to your own organization's servers, or you can pick another from the **Organization** filter. {% hint style="info" %} **Still prefer the old page?** A notice at the top of the list links back to the previous Compute page in the older portal, if you'd rather use the familiar view for now. {% endhint %} ## Related topics * [Server details](/organizations/server-details.md) * [Server labels](/organizations/server-labels.md) * [Traffic alerts](/organizations/server-traffic-alerts.md) * [Server usage](/organizations/server-usage.md) * [Organizational units](/organizations/organizational-units.md) * [Importing an organization](/organizations/importing-an-organization.md) * [Compute](/compute.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/servers-page.md?ask=&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.