> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/concepts/registry-visibility.md).

# Registry visibility

Understand the difference between private and public registry visibility in Harness Artifacts and how to choose the right access model for each registry.

Registry visibility is the access model for a registry; it determines who can see its contents and pull from it, and whether they need credentials to do so.

Every registry you create in Harness Artifacts has a visibility setting. Most registries should be private, and the cases where public visibility is appropriate are narrow and deliberate.

## Private registries

**Private is the default** for every new registry. With private visibility:

* Viewing registry contents requires authentication.
* Pulling artifacts requires authentication and the appropriate RBAC permission.
* Pushing artifacts requires authentication and write permission.

Private registries are appropriate for every case where access should be controlled: internal application images, proprietary libraries, build artifacts, packages containing code you own, and any registry in a compliance-regulated environment where access must be audited. If in doubt, private is the correct choice.

## Public registries

With public visibility, anyone with the registry URL can view artifacts and pull them without credentials. Pushing always requires authentication, regardless of visibility.

Public registries are appropriate when you intentionally want open, unauthenticated access, typically for distributing software to the community or to external users who cannot be expected to manage Harness credentials.

Common scenarios:

* An open-source project distributing Docker images or packages to the community.
* Shared base images that teams across your organization (including teams outside your Harness account) need to pull without credential management overhead.
* Developer CLI tools or libraries you want external users to install directly.

Public visibility should not be used for internal packages, packages with proprietary code, or registries in environments subject to Payment Card Industry Data Security Standard (PCI DSS), Health Insurance Portability and Accountability Act (HIPAA), or similar regulations where every access event must be tied to an authenticated identity.

## Enable public visibility

{% hint style="success" %}
The Public registry visibility feature is in [Limited GA](#user-content-fn-1)[^1] and requires enablement. [View all early access features.](https://developer.harness.io/release-notes/features.md)

{% @harness-feature-flag-access/request-feature-flag-access module="artifacts" pagePath="artifacts/concepts/registry-visibility" pageTitle="Registry%20visibility" featureFlags="%5B%7B%22name%22%3A%22Public%20registry%20visibility%22%2C%22key%22%3A%22PL\_ALLOW\_TO\_SET\_PUBLIC\_ACCESS%22%2C%22status%22%3A%22LIMITED\_GA%22%2C%22description%22%3A%22Enables%20the%20Public%20visibility%20option%20for%20registries%2C%20allowing%20unauthenticated%20pull%20access%20to%20artifacts.%22%2C%22section%22%3A%22enable-public-visibility%22%7D%5D" %}
{% endhint %}

After Harness enables public registry visibility for your account, go to **Account Settings** > **Authentication** and enable **Allow public resources**. Both conditions are required before the **Public** option appears in the Create Registry form or the Configuration tab of an existing registry.

## Changing visibility

You can switch a registry between private and public at any time from its **Configuration** tab. Changing visibility does not move, copy, or delete any artifacts. It changes only the access model: after switching a registry to public, previously authenticated pulls become unauthenticated; after switching back to private, unauthenticated access stops immediately.

## Visibility is per-registry, not per-account

Each registry has its own visibility setting, independently of any other registry in your account. An account-level registry can be public while project-level registries in the same account remain private. A public registry in one organization does not affect registries in other organizations.

This makes it possible to maintain a clean separation: a single public registry for community distribution alongside private registries for all internal work, all within the same Harness account.

## Use cases

**Open-source distribution alongside private CI artifacts**

A team maintains an open-source project. They create one public registry for their published Docker images and packages and a separate private registry for the build artifacts generated by their CI pipeline. The published images are freely accessible; the CI builds are not.

**Internal shared libraries with controlled access**

A platform engineering team publishes internal shared libraries to an organization-scoped private registry. Only teams within that organization can pull from it. Developers in other organizations must request access through the platform team, creating a deliberate approval step.

**External CLI tooling with frictionless installation**

A tools team builds a developer CLI and wants external users to install it with a single pull command, without creating a Harness account. They publish the CLI binaries to a public registry. The installation command works without credentials for any user anywhere.

## Next steps

To set or change visibility on a registry, go to [Set registry visibility](https://developer.harness.io/artifact-registry/3.0/registries/set-registry-visibility.md).

{% @harness-feedback/feedback %}

[^1]: On by default, ready for production use and rolling out to every Harness environment incrementally. If you want it before it reaches your environment, request access and Harness will turn it on for your account. Rollout happens in stages, so a feature can reach some environments a week or two before others. Harness can also turn it off via the same **Request access** process for your account if you need it off.
