> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/system-admins/administration/job-manager/system-messages/remote-systems.md).

# Remote systems

Review and administer remote-system definitions used by system messages.

Open `System messages` > `Remote systems` to review connected-system definitions used by system messages.

## Find a remote system

Search by remote-system identifier, description, or another displayed value. Select a result to open its details and related messages.

## Create or edit a remote system

The create, edit, save, and delete controls require `COMMON_ADMIN`.

1. Select the create action or open an existing remote system.
2. Enter the required connection and identification fields.
3. Review the identifier before the first save. An existing identifier can be read-only.
4. Enter secrets only through the protected form fields.
5. Select `Save`.
6. Reopen the remote system and confirm its non-secret values.

Never copy a secret from this page into documentation, chat, an issue, or a screenshot.

Delete a remote system only after you confirm that message types, integrations, and existing messages no longer depend on it.

## Review related messages

Use search, status filters, and pagination to inspect messages associated with the remote system. Select a message to open its detail.

See [Trace a system message](https://docs.hotwax.co/documents/system-admins/administration/job-manager/system-messages/message-details.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.hotwax.co/documents/system-admins/administration/job-manager/system-messages/remote-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.
