> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/orbit/en/powerio-orbit.md).

# powerIO Orbit

powerIO Orbit is powerIO's cloud platform for building automation: projects, software versions, and devices in one place, for your entire team.

<figure><picture><source srcset="/files/9449d1fe0fe2f89026d889029bc51857d05ce308" media="(prefers-color-scheme: dark)"><img src="https://4132839365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcCl0f7fHRZGoIU6rAFRD%2Fuploads%2Fgit-blob-a0191204bea6b7bd08e34c4e6df6a061b5cb6229%2Forbit-03-extension_color_animated.svg?alt=media" alt="Logo von powerIO Orbit mit zwei kreisenden Umlaufbahnen" width="360"></picture><figcaption></figcaption></figure>

Every system gets its fixed place in Orbit. The project for its control system is right next to it, along with all versions, as are system schematics and logs. Orbit runs in the browser; no installation is required.

<a href="https://orbit.powerio.com" class="button primary" data-icon="rocket-launch">Request access</a> <button type="button" class="button secondary" data-action="ask" data-icon="gitbook-assistant">Ask a question about powerIO Orbit</button>

{% hint style="info" %}
This documentation shows powerIO Orbit with an English interface. Names of buttons, menus, and fields are shown in bold and exactly as in Orbit, for example **Projects** or **Invite user**.
{% endhint %}

## Features at a glance

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-gauge" style="color:$primary;">:gauge:</i></h4></td><td><h4>Dashboard</h4></td><td>The <strong>Dashboard</strong> shows the number of users, devices, projects and software archives. In addition, there are the latest activities and your favorites.</td><td><a href="/hub/orbit/en/getting-started/oberflaeche.md">Interface overview</a></td></tr><tr><td><h4><i class="fa-sitemap" style="color:$primary;">:sitemap:</i></h4></td><td><h4>Projects</h4></td><td>Under <strong>Projects</strong> you map your systems as a tree. An <strong>Item</strong> stores a CODESYS project as a software archive, for example, along with attachments with version history.</td><td><a href="/hub/orbit/en/projects/projekte.md">Projects and items</a></td></tr><tr><td><h4><i class="fa-box-archive" style="color:$primary;">:box-archive:</i></h4></td><td><h4>Repository</h4></td><td>The <strong>Repository</strong> lists all software archives of your organization with project path, last upload and number of versions.</td><td></td></tr><tr><td><h4><i class="fa-circle-nodes" style="color:$primary;">:circle-nodes:</i></h4></td><td><h4>Devices</h4></td><td>Under <strong>Devices</strong> you can see your powerIO devices with status, firmware version and last contact.</td><td></td></tr><tr><td><h4><i class="fa-user-group" style="color:$primary;">:user-group:</i></h4></td><td><h4>Users</h4></td><td>Under <strong>Users</strong> invite people by e-mail and assign roles. You can create your own roles in the tab <strong>Roles</strong> there.</td><td><a href="/hub/orbit/en/users-and-roles/rollen-und-berechtigungen.md">Roles and permissions</a></td></tr><tr><td><h4><i class="fa-clock-rotate-left" style="color:$primary;">:clock-rotate-left:</i></h4></td><td><h4>Audit</h4></td><td>Under <strong>Audit</strong> you can see who changed what in your organization. Deleted content can be restored depending on your plan in the tab <strong>Restore</strong> back.</td><td><a href="/hub/orbit/en/administration/audit-und-papierkorb.md">Audit log and recycle bin</a></td></tr></tbody></table>

## Getting started with powerIO Orbit

The path to Orbit begins with registration at <code class="expression">space.vars.orbit\_url</code>. The following pages guide you in this order from the approval list to the first software archive.

{% content-ref url="/pages/bd6c3934bcd39e67da96a797c0ef68dee075e778" %}
[Request access and get started](/hub/orbit/en/getting-started/zugang-beantragen.md)
{% endcontent-ref %}

{% content-ref url="/pages/da0dd80e07bae2e94272b0038fb5e334b7016964" %}
[Interface overview](/hub/orbit/en/getting-started/oberflaeche.md)
{% endcontent-ref %}

{% content-ref url="/pages/1400f2da90488ec1c2e4e118b9d9cfb5ac6c610d" %}
[Create and structure a project](/hub/orbit/en/projects/projekte/projekt-anlegen.md)
{% endcontent-ref %}

{% content-ref url="/pages/45a50662472dc64bd4376ef834ac304954bf5e30" %}
[Upload software archive](/hub/orbit/en/projects/projekte/softwarearchiv-hochladen.md)
{% endcontent-ref %}

{% content-ref url="/pages/3ecea776173e73730d6d6442fdb855504f5e2ce0" %}
[Invite user](/hub/orbit/en/users-and-roles/benutzer-einladen.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

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

```
GET https://support.powerio.com/hub/orbit/en/powerio-orbit.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 `build a script that syncs our docs to a CMS` 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.
