> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.cloudquant.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dataset Visibility

> Control whether datasets are public (discoverable by all authenticated users) or private (entitlement required)

# Dataset visibility

Every dataset has a **Publicly Available** toggle that controls whether authenticated users can discover and query it without an individual entitlement.

| Visibility  | UI toggle                  | Who can see and query                                     |
| ----------- | -------------------------- | --------------------------------------------------------- |
| **Public**  | **Publicly Available** ON  | Any authenticated user — no per-user entitlement required |
| **Private** | **Publicly Available** OFF | Only users with an explicit entitlement                   |

Authentication is always required. Unauthenticated requests never return datasets.

<Note>
  Visibility and entitlements are separate. A **private** dataset still requires an entitlement assignment on the [Users](/administration/managing-users-and-entitlements) page. A **public** dataset is queryable by any signed-in user without that step.
</Note>

## Who can change visibility

| Role            | Can set public / private |
| --------------- | ------------------------ |
| **Super Admin** | Yes                      |
| **Admin**       | Yes                      |
| **User**        | No                       |

## Set visibility during onboarding

<Steps>
  <Step title="Open the wizard">
    As Admin or Super Admin, go to **Datasets → Add Dataset**.
  </Step>

  <Step title="Configure the dataset">
    Proceed through source, connection, and columns.
  </Step>

  <Step title="Set Publicly Available">
    Near the top of the configuration page, set **Publicly Available** ON (public) or OFF (private).
  </Step>

  <Step title="Save">
    Complete the wizard and save. The setting takes effect immediately.
  </Step>
</Steps>

## Change visibility on an existing dataset

1. Go to **Datasets** in the admin portal.
2. Use the **Public** column in the list to audit current visibility at a glance.
3. Open the dataset, toggle **Publicly Available**, and save.

Making a public dataset private hides it from non-entitled users immediately.

## API and catalog behavior

* **Private** datasets do not appear in catalog browse or search for users without entitlement.
* **Public** datasets appear in the catalog for any authenticated user.
* Use `liberator.datasets(entitled=True)` to list datasets you can access (entitlements plus public datasets you are allowed to see). See [Checking dataset access](/python-guide/dataset-access) and [Listing datasets](/api-reference/concepts/listing-datasets).

## Pre-generated cache

Visibility does not change cache behavior. Pre-generated cache continues to serve entitled users if you switch a dataset from public to private.

## Recommended practices

* **Public** — shared reference data (calendars, instrument masters) that all users need.
* **Private** — client-specific, team-scoped, or sensitive datasets.
* Audit the **Public** column periodically; test datasets left public during onboarding are a common oversight.

## Troubleshooting

**User cannot see an expected dataset** — If private, confirm entitlement on the Users page. If public, confirm the user can authenticate.

**Dataset visible to users who should not see it** — Set **Publicly Available** OFF and save.

**Toggle not visible** — Confirm you are signed in as Admin or Super Admin.