> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/administration-new-ui/general-settings/registry.md).

# Registry

Define registries and access scoping for fleets in JFrog Connect.

When you use JFrog Connect to deploy software to edge devices, the Connect Agent pulls the software image from a designated registry (such as JFrog Registry, Git, or DockerHub) where the image is stored.

When you use Connect for the first time, one [JFrog registry](/administration-new-ui/general-settings/registry/add-jfrog-registry.md) is already configured in Artifactory. Before you can use this registry, you have to define the [access scoping](/administration-new-ui/general-settings/registry/add-artifactory-access-scope.md). For any additional JFrog registries that you create, you will follow a simple two-step process:

1. Add the JFrog registry.
2. Configure Artifactory Access Scoping for that registry.

This process ensures that you have proper access controls in place for effective management of your software deployment.

### Additional Registries

To define registries in addition to the default registry, use the procedures as indicated below. Registries that are not JFrog do not include access scoping.

| Registry                                                            | See…                                                                                                  |
| ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Additional JFrog registries (Artifactory)                           | [Add JFrog Registry](/administration-new-ui/general-settings/registry/add-jfrog-registry.md)          |
| Artifactory Edge                                                    | [Add JFrog Registry](/administration-new-ui/general-settings/registry/add-jfrog-registry.md)          |
| Private Git                                                         | [Add Private Git](/administration-new-ui/general-settings/registry/add-private-git.md)                |
| Private Docker Registry with providers AWS ECR, DockHub, or private | [Add Private Docker Registry](/administration-new-ui/general-settings/registry/add-private-docker.md) |

## What’s Next?

Learn how to add an [Artifactory Access Scope](/administration-new-ui/general-settings/registry/add-artifactory-access-scope.md) to your first JFrog registry and to additional JFrog registries.


---

# 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.connect.jfrog.io/administration-new-ui/general-settings/registry.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.