> 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/registries/set-registry-visibility.md).

# Set registry visibility

Set a registry to Private so only authenticated users can access it, or to Public so anyone can pull artifacts without authentication.

{% hint style="success" %}
This 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/registries/set-registry-visibility" pageTitle="Set%20registry%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%7D%5D" %}
{% endhint %}

Every registry in Harness Artifacts has a visibility setting that controls who can view its contents and pull from it.

* **Private**: only users and service accounts with the required permissions or a valid identity token can view the registry and pull artifacts.
* **Public**: anyone can view the registry contents and pull artifacts without authentication. Pushes still require authentication regardless of visibility.

You can set visibility when you create a registry, or change it at any time from the registry's configuration.

{% hint style="info" %}
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 registry form.
{% endhint %}

## Set visibility on a new registry

Visibility is one of the fields on the **Create a new artifact registry** drawer. Select **Private** or **Public** before you click **Create registry**.

Go to [Create a registry](https://developer.harness.io/artifact-registry/3.0/registries/create-a-registry.md) for the full creation walkthrough.

## Change visibility on an existing registry

1. In the navigation menu, select **Registries**.
2. Click the registry you want to update.
3. Select the **Configuration** tab.
4. In the **Definition** section, find the **Visibility** field and select **Private** or **Public**.
5. The change saves automatically when you close the edit drawer.

## Visibility and the Registries list

The **Registries** list shows a **Visibility** column for each registry. You can see at a glance which registries are public without opening each one.

## Considerations

* Making a private registry public means anyone with the registry URL can pull its artifacts. Review the contents before changing visibility.
* Harness does not send a notification when registry visibility changes. Communicate the change to your team if downstream consumers rely on authentication.
* Public visibility applies to pull operations only. Pushes always require a valid identity token, even for public registries.

## Next steps

* [Create a registry](https://developer.harness.io/artifact-registry/3.0/registries/create-a-registry.md)
* [RBAC and permissions](https://developer.harness.io/artifact-registry/3.0/reference/rbac-and-permissions.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.
