> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/medcrypt-documentation/guardian/manage-systems.md).

# Manage systems

{% hint style="warning" %}
🚧 This feature is currently in development.
{% endhint %}

## **Overview**

The Systems page provides visibility into your various systems, as well as access to essential system management tools, including:

* **Download system provisioning packages** Access and download provisioning packages directly from the Guardian Cloud UI for streamlined device setup processes.
* **View and export Root of Trust certificates** Manage your PKI infrastructure by viewing and exporting root and intermediate level certificates, providing complete oversight of your certificate management.

## Manage systems

1. Click the **Systems** item in the sidebar. This will display your available systems.
2. Click the Provisioning packages link on the system card. This will display the **Provisioning packages** tab.
3. Click **Download** on the provisioning package card to download that system provisioning package.
4. Click the **Certificates** tab. This will display the root and intermediate certificate trust chain for the selected system.
5. Click any certificate to view its details.

### Systems cards

Each system card displays the following information:

* **System name:** This displays the name of the system, also known as the system definition.
* **Last updated:** This reflects the date the system configuration was last updated.
* **Approval type:** This is the device provisioning approval workflow for this system (**Automatic** or **Manual**).
* **Provisioning source:** This is the source by which your devices are provisioning (**Cloud** or **Appliance**).
* **Components:** The components in your system.

#### System status badges:

* **Complete configuration:** If you've started configuring a system that is still in draft mode, you can click this badge or link to finish your configuration.
* **Download package:** When your system provisioning package is ready, you can click this badge or the **Provisioning package** link to download the package.
* **Provisioned:** If all devices in your system are provisioned, this badge will display. You can still download provisioning packages or manage the certificate trust chain.

### Provisioning packages

The **Provisioning packages** tab displays if you click the system name or **Provisioning package** link on the system card. If a system's provisioning package is ready for download, the **Download** button will be enabled.

### Certificates: Manage trust chain

Click the [Certificates](/medcrypt-documentation/guardian/manage-systems/manage-certificate-trust-chain.md) tab on any system card to manage root and intermediate (Root of Trust) certificates for your system.


---

# 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.medcrypt.com/medcrypt-documentation/guardian/manage-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.