Skip to main content
Sometimes a dataset is safe to share broadly except for a few sensitive columns — personal identifiers, embargoed measurements, or anything that shouldn’t travel with the rest of the data. DataErai lets you set a visibility policy per field on a dataset.

​
Field visibility

Each field in a dataset has a visibility:
VisibilityWho can see it
PublicAnyone who can read the dataset (the default).
RestrictedOnly viewers who are explicitly granted access to restricted fields.
HiddenWithheld from normal access entirely.
A field policy is set on the dataset, so it survives re-uploads and new versions — governance stays in place as the data evolves.

​
How restricted fields behave

When someone views a dataset, restricted fields are filtered out of what they see unless they hold the extra grant. This applies consistently wherever the dataset’s data is read, so a restricted column doesn’t leak through any view. Granting access to restricted fields is part of the dataset’s Admin role — see Sharing & permissions.
Restricted fields stay protected even when a dataset is shared publicly. Public viewers see only the public fields.

​
Next steps

Sharing & permissions

Roles and how access cascades.

Datasets & versions

Where field policies apply.