> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/datasets/publishing-and-unpublishing-datasets.md).
# Publishing and Unpublishing Datasets
How to share (publishing) and stop sharing (unpublishing) with collaborators.
When you import a dataset, it is unpublished by default. You can choose to publish it to share with other collaborators that have the View Datasets and Data Schema policy set. To learn more, see [Viewing Your Project's Permissions Policy.](/projects/creating-a-new-project.md#configure-permissions) Also, if you have sensitive data, review the options you have for sharing that data before continuing. For more information, see [Sensitive Datasets](/datasets/sensitive-datasets.md).
### Publishing Datasets
To publish a dataset, complete the following steps.
{% stepper %}
{% step %}
#### Select publish from the three-dot menu.
{% endstep %}
{% step %}
#### A message appears asking if you would like to publish the dataset.
If you want to unpublish previously published versions of the dataset, leave the button for that option selected. Otherwise, deselect it.
{% endstep %}
{% step %}
#### Select the Publish Dataset button.
All other participants granted permission to view published datasets will be able to see the dataset. The Publish badge appears on the dataset entry in the Datasets screen.
{% endstep %}
{% endstepper %}
### Unpublishing a Dataset
To unpublish a dataset, complete the following steps.
{% stepper %}
{% step %}
#### Select unpublish dataset from the three-dot menu.
{% endstep %}
{% step %}
#### A message appears asking you if you want to unpublish the dataset.
{% endstep %}
{% step %}
#### Select Unpublish Dataset.
All other participants are no longer able to see the dataset.
{% endstep %}
{% endstepper %}
### Troubleshooting Publishing Issues
This section addresses common errors encountered when attempting to publish datasets or data schemas.
The "Publish" option is not on the menu
* **Cause:** The project's site-level permission for **"View Datasets and Data Schemas"** is likely set to **Full Visibility**(all of the personas have access to the dataset or data schema).
* **Solution:** In Full Visibility mode, all objects are shared with all project members by default; therefore, manual publishing is not required or available. To enable private drafting, a Project Lead must change the permission setting to **Partial Visibility**(only some of the personas have access to the dataset or data schema).
Error: "Cannot Publish Dataset" (Schema Ownership)
* **The Issue:** You are trying to publish a dataset, but the action is blocked.
* **The Message:** *"The associated Data Schema version \[Name] is currently unpublished and is owned by another workgroup."*
* **Why this happens:** To ensure data integrity, a dataset cannot be public if its schema is private. Because the schema belongs to a different workgroup, you do not have the authority to publish it yourself.
* **How to fix:**
1. Identify the owner of the Data Schema.
2. Request that they **Publish** the specific schema version.
3. Once the schema is published, retry publishing your dataset.
The Data Schema published automatically
* **The Scenario:** You published a dataset, and its associated schema status changed to "Published" without manual intervention.
* **Explanation:** If your workgroup owns both the dataset and the unpublished schema version, the Rhino FCP automatically publishes the schema to prevent broken dependencies.
* **System Prompt:** You should receive a confirmation dialog stating: *"Publishing this dataset will automatically publish the associated Data Schema version. Do you wish to proceed?"*
The Code Object or Dataset suddenly became "Unpublished"
* **Cause:** A user (likely a Data Custodian or Schema Owner) has **Unpublished the underlying Data Schema**.
* **The Logic:** Data Schemas are foundational. If a schema is pulled from public view, all "downstream" objects—such as Datasets that follow that schema or Code Objects that use it for input/output—are automatically unpublished to maintain privacy and system consistency.
* **Solution:** Republish the Data Schema to restore visibility to the associated datasets and code.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.rhinofcp.com/datasets/publishing-and-unpublishing-datasets.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.