> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/connected-systems.md).

# Connected Systems

A connected system groups work and agent assignments. When a job has to run on a particular agent, for example one installed next to a specific platform, you assign that agent and the work to the same system. Use this tab to register systems and check their agent coverage.

Open it from **Administration** → **Global Settings** → **Connected systems** in the sidebar.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fa56wgT4UbHH2xDodeoLc%2Fv2-gs-systems.png?alt=media&amp;token=a1eca354-cc34-4473-b165-a35ab03dc08e" alt="Connected systems tab with summary tiles and the system inventory"><figcaption><p>Connected systems</p></figcaption></figure>

{% hint style="warning" %}
You need a role that can view systems to open this tab. Registering, editing and deleting systems each need their own system permission.
{% endhint %}

{% hint style="info" %}
Registering a system does not connect to it or check its health. Assignments describe collection scope; check agent heartbeats and execution results to see whether work is actually running.
{% endhint %}

## Summary Tiles

| Tile                      | Shows                                                                                  |
| ------------------------- | -------------------------------------------------------------------------------------- |
| **Registered systems**    | Systems matching the current search.                                                   |
| **Assigned to agents**    | Systems with at least one agent assigned.                                              |
| **Without an assignment** | Systems no agent is assigned to. Review whether that is the intended collection scope. |

## System Inventory

Use **Search system names or keys** to filter the table. **Reset filters** clears the search, the number of records shows beside **Refresh**, **Columns** chooses the columns to show and **Export** downloads the list. **Export this page** at the top of the tab downloads the systems on the current page as a CSV file.

| Column                | Description                                                       |
| --------------------- | ----------------------------------------------------------------- |
| **System**            | The system's name (click it to open **System evidence**) and key. |
| **Agent assignments** | How many agents are assigned, or **No explicit assignment**.      |
| **Last updated**      | When the system last changed.                                     |
| **Review**            | **Review system** opens **System evidence**.                      |

**System evidence** shows the system's name, key, registration and update dates, number of agent assignments and identity, and the **Assigned agents** with their recorded state. From there you can:

* Edit the system.
* Click **System executions** to open the execution history filtered to this system.
* Click **Delete system** to delete the registration after typing its exact name.

{% hint style="danger" %}
Deleting a system also deletes its agent assignments and can affect configuration that uses it. Review the linked agents and executions first.
{% endhint %}

## Register a System

1. Click **Register system**.
2. Enter the **System name** and **System key**.
3. Click **Save changes**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FHnBt8EKtIelLEuz954qw%2Fv2-gs-systems-register.png?alt=media&amp;token=3b49d2ff-e430-4bb1-9268-45a1a9bd1f44" alt="Register system form with System name and System key"><figcaption><p>Register system</p></figcaption></figure>

| Field           | Description                                                                         |
| --------------- | ----------------------------------------------------------------------------------- |
| **System name** | **Required.**                                                                       |
| **System key**  | **Required.** Use the stable key that your configuration and integrations refer to. |

{% hint style="warning" %}
Changing the key of an existing system can affect configuration that refers to it by key.
{% endhint %}

To assign an agent to a system, edit the agent and add the system under **Assigned systems**.

## Next Steps

* [Agents](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/agents.md): assign agents to a system.
* [Execution History](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules/execution-history.md): follow the work recorded against a system.
* [Global Settings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings.md): the other configuration screens.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/connected-systems.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.
