> 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-release-the-identities-of-authors-of-accepted-papers-only.md).
# How to release the identities of authors of accepted papers only
Author identities stay hidden when submissions are released, unless you change the **Form Fields** of a release step. The **Accepted Submission Release** step releases submissions with an accepting decision, and the **Rejected Submission Release** step releases the rest. To reveal the authors of accepted papers only, change the **Accepted Submission Release** step and leave the **Rejected Submission Release** step as it is.
1. Go to your venue's [Workflow Timeline](/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#workflow-timeline) and find the **Accepted Submission Release** step. The Workflow Timeline lists it as **Create Accepted Submission Release**.
2. Click **Edit** next to **Form Fields**.
3. In the **Content JSON** tab, change the `readers` of the `authors` field to:
```json
{
"authors": {
"readers": { "const": { "delete": true } }
}
}
```
Leave the other fields as they are.
4. Click **Submit**.
5. Click **Edit** next to **Readers** and choose who can read accepted submissions. The authors are revealed to everyone who can read the submission, so select **Public** to show the authors of accepted papers to everyone.
6. Click **Edit** next to **Dates**, set the **Activation Date** to when accepted papers should be released, and click **Submit**.
The default Form Fields of Create Accepted Submission Release, before the authors entry is changed.
When the step runs, the authors of accepted papers are shown on the submission and included in its BibTeX. Rejected submissions keep their authors hidden, and their BibTeX lists the author as Anonymous.
{% hint style="info" %}
After the Activation Date has passed, the step runs again each time you edit it. To hide the authors again, set the `readers` of the `authors` field back to a list of readers, such as `["", "/Submission${{4/id}/number}/Authors"]`.
{% endhint %}
For how to make the papers themselves public, see [How to make papers public after decisions are made](/how-to-guides/workflow/how-to-make-papers-public-after-decisions-are-made.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-release-the-identities-of-authors-of-accepted-papers-only.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.
