> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/how-to-guides/workflow/how-to-make-papers-public-after-decisions-are-made.md).
# How to make papers public after decisions are made
Your venue's [Workflow Timeline](/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#workflow-timeline) has two steps that release submissions once decisions are posted:
* **Accepted Submission Release** updates submissions whose decision is one of the accept options. They are marked as accepted and get a publication date.
* **Rejected Submission Release** updates all other submissions that have a decision. They are marked as rejected.
Submissions without a decision are not changed by either step. Both steps run automatically on their **Activation Date**. By default, they release submissions to the Program Chairs, the assigned Senior Area Chairs, Area Chairs and Reviewers, and the submission's authors. Submissions are not made public unless you select **Public**.
1. Make sure all decisions are posted and that the accept options are correct. In the **Decision** step, click **Edit** next to **Decision Options** and check the **Accept Decision Options**.
2. Find the **Accepted Submission Release** step. The Workflow Timeline lists it as **Create Accepted Submission Release**.
3. Click **Edit** next to **Readers**, select **Public**, and click **Submit**.
4. Click **Edit** next to **Dates**, set the **Activation Date** to when the accepted papers should be released, and click **Submit**.
5. Repeat steps 3 and 4 in the **Rejected Submission Release** step. To keep rejected submissions private instead, select the readers who should keep access, for example **Program Chairs** and **Submission Authors**.
The Create Accepted Submission Release step, as Program Chairs see it.
**Public** can't be combined with other options. If you don't select **Public**, you must select **Program Chairs**.
{% hint style="info" %}
Releasing submissions doesn't reveal the authors' identities. To show author names on accepted papers only, see [How to release the identities of authors of accepted papers only](/how-to-guides/workflow/how-to-release-the-identities-of-authors-of-accepted-papers-only.md).
{% endhint %}
{% hint style="info" %}
After the Activation Date has passed, a release step runs again each time you edit it. If a decision changes after the release, edit both release steps again, for example by submitting their **Dates** again, so the submission is released by the step that matches its new decision.
{% endhint %}
Decisions have their own release step. To choose who can read the decisions, use the **Decision Release** step, in the same way as described in [How to release reviews](/how-to-guides/workflow/how-to-release-reviews-decisions-and-metareviews.md).
---
# 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.openreview.net/how-to-guides/workflow/how-to-make-papers-public-after-decisions-are-made.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.
