> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/publish-and-unpublish-a-project.md).

# Publish and unpublish a project

Publish a workflow to make a selected version available to its users. You can continue to edit the draft without changing the published version.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FneCUnUJEuS54pa5SPUJE%2FG069.mp4?alt=media&token=12fb44ff-de59-487b-864d-9f58da8da9c7>" %}

## Before you start

Start with a saved, tested project and permission to publish it. If your project requires approval or uses deployment stages, follow [Create a project pull request](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/create-a-project-pull-request.md) and [Deployments and approval requirements](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/deployments-and-approval-requirements.md) instead of expecting a direct Publish Version action. Decide whether you are releasing a correction or intentionally stopping access before using Unpublish.

## Publish the workflow

Run the draft with representative input and inspect Output.

![Draft test output](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/LLqVq2rJ4R4JWstqU9oa/assets/g069-g069-01-tested.png)

Confirm the actual behavior before making that version available to users.

Select Publish, describe the change, and choose Publish Version.

![Publish Version dialog and change description](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/DpphG0tgHm1fUec6F9l1/assets/g069-g069-02-publish.png)

Use a description that helps reviewers understand the change and the checks performed.

Open the published interface and submit a request in a fresh conversation.

![Published interface response](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/Hcy3GGMZ4kx7gkF78hzI/assets/g069-g069-03-published.png)

Confirm that the live response uses the version you intended to release.

## Continue editing the draft

Make the next change in the workflow draft and run it.

![Changed draft and test result](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/XbEnKbTyy6ji1tdM3WOq/assets/g069-g069-04-draft-two.png)

Inspect the new result before requesting another publication.

Open the published interface again and compare its behavior with the changed draft.

![Published interface after a draft edit](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/MbOMEEJMsbHF90QAKbvj/assets/g069-g069-05-still-published.png)

Draft edits do not replace the live release until they are published.

## Unpublish a workflow

Use the publication control to unpublish the project when it should no longer be available.

![Unpublish control and publication status](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/rPMussf1dycqhxS9pCeB/assets/g069-g069-06-unpublished.png)

Reopen the former published URL to confirm that the interface is no longer accessible there.

## Important behavior

Saving changes updates the draft. Publish a new version when you want those changes to reach the published interface.

Unpublishing makes the published interface unavailable. Use it only when you intend to stop access.


---

# 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.stackai.com/guides-and-quickstarts/releases-and-environments/publish-and-unpublish-a-project.md?ask=<question>&goal=<user_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.
