> 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-change-who-can-access-submissions-after-the-deadline.md). # How to Change Who can Access Submissions After the Deadline At any point during your venue's worflow, you can click on the ‘Post Submission’ button and use the field ‘Submission Readers’ to change the readers for all submissions: * **All program committee (all reviewers, all area chairs, all senior area chairs if applicable)**: all papers are private and only released to all reviewers, area chairs and senior area chairs (if your venue has them) * **Assigned program committee (assigned reviewers, assigned area chairs, assigned senior area chairs if applicable)**: all papers are private and only released to each paper's assigned reviewers, area chairs and senior area chairs (if your venue has them) * **Program chairs and paper authors only**: papers are private and released only to program chairs and paper authors * **Everyone (submissions are public)**: papers are released to the public You can use this field to change the submission readers as many times as needed. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.openreview.net/how-to-guides/workflow/how-to-change-who-can-access-submissions-after-the-deadline.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.