> 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/harness-ai/use-harness-platform/pipelines/executions-and-logs/allow-public-access-to-executions.md).

# Allow public access to pipeline executions

Enable public access to pipeline executions so you can share execution URLs without requiring users to sign in to Harness.

You can enable public access to pipeline executions, allowing you to share execution URLs with users who do not have Harness accounts. When you enable this feature, pipeline executions for pipelines marked for public view become accessible without requiring sign-in to Harness.

{% hint style="info" %}

* When you mark a pipeline for public view, console logs for all steps in the pipeline are also publicly accessible.
* This feature requires the `PL_ALLOW_TO_SET_PUBLIC_ACCESS` feature flag. Contact [Harness Support](mailto:support@harness.io) to enable it.
  {% endhint %}

***

## What you will learn from this topic

* How to [enable public access](#enable-public-access-to-resources) at the account level.
* How to [mark individual pipelines](#enable-pipelines-for-public-view) for public view.

***

## Before you begin

* **Harness account admin access:** You need account administrator permissions to enable public access at the account level. Go to [RBAC in Harness](/harness-ai/use-harness-platform/platform-access-control.md) to understand role-based access control.
* **Pipeline edit permissions:** You need **Create/Edit** permission on [Pipelines](/harness-ai/use-harness-platform/platform-access-control/permissions-reference.md#pipelines) to mark pipelines for public view. To get this permission, an administrator must assign you a role that includes it. Go to [Manage roles](/harness-ai/use-harness-platform/platform-access-control/add-manage-roles.md) to configure role assignments.
* **Feature flag enabled:** Ensure the `PL_ALLOW_TO_SET_PUBLIC_ACCESS` feature flag is enabled for your account.

***

## Security considerations

Before enabling public access to pipeline executions, consider the following security implications:

* **Console logs are public:** All console logs for steps in public pipelines are accessible without authentication. Ensure logs do not contain sensitive information such as credentials, API keys, or proprietary data.
* **Execution details are visible:** Pipeline execution details, including input/output variables, stage information, and execution metadata, are visible to anyone with the execution URL.
* **No access control:** Public executions bypass Role-Based Access Control (RBAC). Anyone with the execution URL can view the execution details.
* **Cannot be revoked individually:** Once an execution is public, you cannot revoke access to individual execution URLs. You must disable public access for the entire pipeline or account.

{% hint style="warning" %}
Only enable public access for pipelines that do not process or expose sensitive information. Review all console logs and outputs before marking a pipeline for public view.
{% endhint %}

***

## Enable public access to resources

Perform the following steps to enable public access to resources at the account level:

1. In your Harness account, navigate to **Account Settings**.
2. Select **Authentication**.
3. Enable the **Allow public resources** toggle.
4. In the confirmation dialog, select **Enable**.

Public access is now enabled at the account level. You can now mark individual pipelines for public view.

***

## Enable pipelines for public view

After enabling public access at the account level, perform the following steps to mark individual pipelines for public view:

1. In Harness, navigate to your pipeline.
2. Select **Advanced Options**.
3. Enable **Mark this pipeline for public view**.
4. Select **Save**.

All future executions of this pipeline will be publicly accessible. Anyone with the execution URL can view execution details and console logs without signing in to Harness.

***

## Next steps

* [View and compare pipeline executions](/harness-ai/use-harness-platform/pipelines/executions-and-logs/view-and-compare-pipeline-executions.md): View compiled YAML and compare execution differences.
* [Download execution logs](/harness-ai/use-harness-platform/pipelines/executions-and-logs/download-logs.md): Download logs from pipeline executions for offline analysis.
* [RBAC in Harness](/harness-ai/use-harness-platform/platform-access-control.md): Understand role-based access control for managing pipeline permissions.

{% @harness-feedback/feedback module="harness-ai" pagePath="harness-ai/use-harness-platform/pipelines/executions-and-logs/allow-public-access-to-executions" %}