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 |
Visibility and entitlements are separate. A private dataset still requires an entitlement assignment on the Users page. A public dataset is queryable by any signed-in user without that step.
Who can change visibility
| Role | Can set public / private |
|---|---|
| Super Admin | Yes |
| Admin | Yes |
| User | No |
Set visibility during onboarding
Set Publicly Available
Near the top of the configuration page, set Publicly Available ON (public) or OFF (private).
Change visibility on an existing dataset
- Go to Datasets in the admin portal.
- Use the Public column in the list to audit current visibility at a glance.
- Open the dataset, toggle Publicly Available, and save.
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 and 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.