> 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/data-schemas/publishing-and-unpublishing-data-schemas.md).
# Publishing and Unpublishing Data Schemas
Rhino FCP allows you to securely publish data schemas so that they are visible to selected collaborators. You can control which versions to publish or unpublish. You can also manage collaborator permissions. Publishing different versions aids model training and refinement, allows version control, and supports development of variations for specific purposes.
Collaborators with access to a dataset using a published data schemas can view inference results. This maintains security and privacy while still allowing result sharing.
### About Publishing and Unpublishing
Publishing makes data schemas visible to all collaborators *who do not already* have permission to view them in the "View Datasets and Data Schemas". When you unpublish a data schema, it will stop being visible to all users except those indicated in the "View Datasets and Data Schemas" permission.
### Prerequisites
Data Schemas are available to all personas listed in the View Datasets and Data Schemas persona in the Site-Level Permissions.
* *If all personas can view datasets and data schemas*, the publishing and unpublishing options *will not be* available because it won't be needed.
* *If some personas do not have the permission to view datasets and data schemas*, the publishing and unpublishing options *will be* available.
For more details, see the [Permissions documentation (View Datasets and Data Schemas Setting)](/projects/persona-and-permissions-policies-reference.md).
### Data Schemas
The following instructions explain how to publish and unpublish a data schema.
### Publishing a Data Schema
{% stepper %}
{% step %}
### Select Data Schema
Select Data Schema from the menu on the left side of the screen.
{% endstep %}
{% step %}
### Open the schema menu
Right-click the three-dot menu next to the data schema you want to publish, then select Publish Schema.
{% endstep %}
{% step %}
### Confirm publishing
A message appears asking whether you would like to publish the data schema. If you want to unpublish all previous versions of the data schema, click the “Unpublish any previously published versions of this schema” checkbox.
> NOTE: If you choose to unpublish a data schema, it will stop being visible to all users without the “View Dataset and Data Schema” permission, and all published data schema will be unpublished.
> {% endstep %}
{% step %}
### **Publish the schema**
Select Publish Schema. The data schema is published and can be viewed by collaborators with the appropriate permissions.
* If you publish a data schema, you can choose to automatically unpublish all previously published versions of the same data schema.
* When you unpublish a data schema, this data schema will stop being visible to all users who do not have the “View Datasets and Data Schemas” permission.
{% endstep %}
{% endstepper %}
#### Unpublishing a Data Schema
{% stepper %}
{% step %}
### Select Data Schema
Select Data Schema from the menu on the left side of the screen.
{% endstep %}
{% step %}
### Open the schema menu
Right-click the three-dot menu next to a data schema that has a highlighted publish icon.
{% endstep %}
{% step %}
### Choose Unpublish
Select Unpublish data schema. A prompt that confirms that you want to unpublish the data schema opens.
{% endstep %}
{% step %}
### Confirm unpublishing
Select Unpublish data schema.
{% endstep %}
{% endstepper %}
### Troubleshooting Publishing Issues
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.