> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/app-maker/developer-tools-and-cli/add-public-key.md).

# Add Public Key

SSH (Secure Shell) serves as a secure means for computers to communicate with each other. It establishes a protected connection over the internet, encrypting the data exchanged between your computer and another computer, ensuring its confidentiality.

In the realm of public-key cryptography, data encryption and decryption are facilitated using a key pair. One of the keys, known as the public key, is shared with others to encrypt data. The other key, the private key, is kept confidential and solely utilized by the owner to decrypt the data. This cryptographic approach ensures secure and private communication between parties involved.

## <mark style="color:red;">Add a Public Key​</mark> <a href="#add-a-public-key" id="add-a-public-key"></a>

To modify the AppMaker managed repository associated with the application in the Akinon ecosystem, users need to add a public key. The responsibility of overseeing this process lies with the developer. It is important to note that up to five public keys can be added for enhanced security and access control.

Public keys belong to your user account, not to an organization. The keys you add here work for the repositories of every organization you are a member of, whichever organization you are working in.

To add a public key, log in to the account and click your avatar (or name) in the top-right corner to open the user menu. Then, click on **Public Keys** to manage and configure the public key settings.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FVM9cnE2zboy3WxCYRF0x%2Fdeveloper-tools-and-cli-add-public-key-public-key-step1.png?alt=media" alt="The Public Keys entry in the user menu, with the Public Keys page behind it"><figcaption></figcaption></figure>

To add a new public key, click on the **+New Public Key** button.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F4DYOGsUEDgeQHD2udVe4%2Fdeveloper-tools-and-cli-add-public-key-public-key-step2.png?alt=media" alt="The +New Public Key button on the Public Keys page"><figcaption></figcaption></figure>

Enter a label for the public key in the **Label** field, and paste the generated SSH Key into the **Public Key** field. Afterward, click the **Apply** button to successfully add the public key to the account.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FKusXZA0b4Tu1evZmEolE%2Fdeveloper-tools-and-cli-add-public-key-public-key-step3.png?alt=media" alt="New Public Key form with Label and Key fields and the Save button"><figcaption></figcaption></figure>

The **Public Keys** list will display the public key that users have added. If they wish to remove a public key, they can click on the delete icon next to the respective key.

{% hint style="info" %}
You can also add a public key by using the AppMaker CLI. For more information on how to do this, refer to the AppMaker CLI documentation.
{% endhint %}


---

# 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.akinon.com/tutorials/app-maker/developer-tools-and-cli/add-public-key.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.
