> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/portal/sign-in-and-security/private-key-storage.md).

# Private key storage

Store your Devolutions Cloud private key using a mobile device, QR code, password, or security key to validate your identity on new devices.

Your Private key is required when accessing your Devolutions Cloud from a new device. You can validate your identity using one of the available storage methods.

All three methods can be enabled simultaneously, and you will always have at least one configured storage option for your Private key. The active storage method is indicated by a green circle with a checkmark, while an unconfigured one is marked with a red circle containing an “X”.

To access the ***Private key storage***, go to the Devolutions Portal and navigate to [***Sign-in & Security***](https://portal.devolutions.com/security).

### Store on a mobile device

This method is recommended because there is no need to remember a password or store your QR code somewhere. This is especially useful for access from a new device or a private browsing session, as your password is not stored in your browser in this situation.

1. Go the ***Store on a mobile device*** section and click ***Configure.***
2. Download [Devolutions Password Manager mobile](https://devolutions.net/workspace/).
3. Once done, click ***Continue***. A QR code will appear.
4. In Devolutions Password Manager mobile, access the Authenticator space.
5. Click ***Add***, then ***Scan a QR code***.
6. Scan the QR code in the browser with your mobile device.

The pairing process will begin. After it ends (it should only take a few seconds), your Private key will be stored on Devolutions Password Manager mobile.

#### Unpair

At any moment, you can decide to delete that storage configuration by clicking on ***Unpair***. This option is useful if you have pairing problems with your mobile device and want to redo the configuration from the start.

### Store as a QR code

If you do not have access to a mobile device or if you want an additional method, this option is the best alternative. Follow the steps below to configure this method.

1. Click ***Configure*** in the ***Store as a QR code*** section.
2. Either ***Download*** or ***Print*** the QR code. Whichever you choose, **be sure to keep it in a safe place**.

#### Regenerate

If you encounter problems using this method to authenticate or if you lost your QR code, you can generate a new one by clicking on the vertical ellipsis and selecting ***Regenerate a new QR Code***. You can also delete the current code without generating a new one by selecting ***Delete Current QR Code***.

{% hint style="warning" %}
Generating a new QR code makes your old code unusable. We therefore recommend that you delete the old code after generating the new one.
{% endhint %}

### Store using a password

1. Click ***Configure*** in the ***Store using a password section***.
2. In the ***Password*** fields, enter a password that follows the specified rules written underneath. Be sure to keep it in a safe place.
3. Click on ***Create password***.
4. If you want to change this password, click on the ***Change password*** icon.
5. Follow the steps, then click ***Change password*** when done.

### Store using a Security key

Click here to learn how to configure a [Security key.](/portal/sign-in-and-security/security-key-and-passkey.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.devolutions.net/portal/sign-in-and-security/private-key-storage.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.