> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/documentation/setup/integrations/managing-container-registry/quay.md).

# Quay

### **Steps to Create a Quay Integration** <a href="#steps-to-create-a-quay-integration" id="steps-to-create-a-quay-integration"></a>

For Personal Access Token permissions and guidelines, follow this link [Quay | In-Product Guides](https://docs.ozone.one/in-product-guides/quay)

**Pre-requisites**

* Access Token/robot access token
* robot user-name
* URL for the provider

**Steps:**

1. Choose the Access type from the drop-down as shown below

i) **Steps to create a Quay Integration**

&#x20;

For Personal Access Token permissions and guidelines, follow this link [![](https://docs.ozone.one/in-product-guides/~gitbook/icon?size=small\&theme=light)Quay | In-Product Guides](https://docs.ozone.one/in-product-guides/quay)

**Pre-requisites**

* Access Token/robot access token
* robot user-name
* URL for the provider

**Steps:**\
\
**1.** choose the Access type from the drop-down as shown below<br>

<figure><img src="/files/DIWXadXUCGxGv1faxI4h" alt=""><figcaption></figcaption></figure>

**(i) Quay Token**

Enter the details required to link your provider for onboarding the repository and click **Create Integration**

<figure><img src="/files/8WYTvPMvCSZ42cc4d6z3" alt=""><figcaption></figcaption></figure>

2. Once the credentials are validated, the integration will be created as shown below, in case of permission issues please refer to the link mentioned above for the permissions required

<figure><img src="/files/zk0uZ9ikJSGnTgDSZB9B" alt=""><figcaption></figcaption></figure>

3. Once the integration is created, the resources will be synced, and the status of the resource synced will be shown on the top left of the integration card ( as shown above - *Success)*\
   \
   Click the card to get a detailed view of the integration created, the user can view the     credentials    and the resources that are synced<br>

   This integration syncs the registry images and tags from Quay

<figure><img src="/files/AZvDiLqSyRrBooIhxx72" alt=""><figcaption></figcaption></figure>

ii) **Quay Robot Token**\
\
Enter the details required to link your provider for onboarding the repository and click **Create Integration**

<figure><img src="/files/P9cY0uoIIKFiX9E6DGrL" alt=""><figcaption></figcaption></figure>

Once the credentials are validated, the integration will be created as shown below, in case of permission issues please refer to the link mentioned above for the permissions required<br>

<figure><img src="/files/zk0uZ9ikJSGnTgDSZB9B" alt=""><figcaption></figcaption></figure>

once the integration is created, the resources will be synced, and the status of the resource synced will be shown on the top left of the integration card ( as shown above - *Success)*

click the card to get a detailed view of the integration created, user can view the credentials and the resources that are synced

This integration syncs the registry images and tags from Quay using a robot account\ <br>

<figure><img src="/files/J20AivrIUx0hCZnmyINU" alt=""><figcaption></figcaption></figure>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ozone.one/ozone-end-user-guide/documentation/setup/integrations/managing-container-registry/quay.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
