To revert a withdrawal, please contact the Program Chairs of your conference using the contact email on the venue homepage.

Individual conferences determine the policy on the visibility of withdrawn and desk-rejected submissions. Please refer to the conference website for further information on the policy, and contact the venue organizers with any questions or concerns.

The author must make sure that the email address associated with the submission is added to their profile and confirmed.

To recruit reviewers, there is a feature located on the venue request form called "Recruitment", clicking this button will allow you to send emails to potential reviewers. To find more information, please see our documentation on Reviewer Recruitment and Reminders.

We understand the frustration, unfortunately, Google Scholar does not have an API that enables us to import author publications.

The best way to get help with a specific issue is to contact the program chairs or organizers of the venue you are participating in. Contact info can usually be found on the venue's OpenReview page.

For general inquiries, you can contact the OpenReview team by using the Feedback Form. We are most responsive from 9AM - 5PM EST Monday through Friday. With the exception of urgent issues, requests made on weekends or US holidays can expect to receive a response on the next business day.

Due date is the advertised deadline.

Expiration date is the hard deadline.

The max file size for uploads is 100 MB.

For Authors

The timeline for submission withdrawals is determined by the Program Chairs of each venue. Therefore, there is not a single overarching OpenReview withdrawal policy. If you have questions about when in a venue workflow you will be able to withdraw your submission, you should reach out to the Program Chairs of that venue directly.

For Program Chairs

Authors are able to withdraw their paper at any time after the submission deadline or after has been run. You can optionally restrict the withdrawal window from your . You can also use the venue request form to configure the visibility of withdrawn and desk-rejected papers, as well as the identities of their authors.

After your venue is deployed, add Program Chair(s) by going to your Venue Request form, clicking the Revision button, then adding the emails of the additional program chair(s) to the Program Chair Emails field of the form. The user will need to have an active OpenReview profile with this email confirmed in order to access the venue.

This is not something that is generated by OpenReview. Please contact the organizers of the venue where you served as a reviewer to see if they can assist you.

To see a history of all emails sent to you by the organizers, please login and go to openreview.net/messages. To see your recent activity, including any reviews you may have submitted, you can go to openreview.net/activity.

There is also the option of you've written with their corresponding submissions using the API.

If you removed the rating or confidence fields from your Official Review form, the PC console will show an average rating and/or confidence of 0 for each paper. If you replaced them with custom values, you can customize your PC console to show the average of those values instead.

1. From your venue request form, click .

2. Select which field you want to be used in place of rating and/or confidence. It must be in the "Additional Review Form Options" field. The options reviewers can select for that field must follow the format "number: description", for example "1: Very Poor".

Sent: The initial status value, meaning the message was sent to the email service.

Dropped: The email was not sent to the recipient for delivery.

Deferred: The email cannot immediately be delivered, but has not been completely rejected. The service will continue to try for 72 hours to deliver the deferred message. After 72 hours the defferal turns into a block.

Bounce: The server cannot or will not deliver the message. This is often caused by outdated or an invalid email address.

Delivered: The email has been accepted by the receiving server. This does not mean that the email made it to the recipient's inbox.

Ensure that you are logged in with an active OpenReview account that has the email the invitation was sent to added and confirmed to it. To make an OpenReview account, see . To add an email to your account, see .

If you are logged in and are still not able to see your assigned submissions (but can see assignments under your Tasks), then reviewers have likely not been given reader access for submissions by the organizers of the venue.

Please contact the venue organizers notifying them of the issue. The contact email can be found on the homepage of the venue.

Reviewers will see their assigned papers in their Reviewer console and in their Task list. Depending on what method you used to assign Reviewers to papers, they may have already been notified of their assignments:

Automatic Assignment Deployed through the Edge Browser

If you deployed an assignment configuration from the edge browser, Reviewers would not have received a notification of their assignments.

Publication date(pdate) means when the venue marked the paper as accepted.

Modification date(mdate) means when the last time the paper was modified.

The odate means when the submission becomes public. To check the odate of a submission, see the note object https://api2.openreview.net/notes?id=

To find the id you can check the url of the submission, for example https://openreview.net/forum?id=KS8mIvetg2 . Use id=KS8mIvetg2 , the note object url will be https://api2.openreview.net/notes?id=KS8mIvetg2.

Participants signing up for an OpenReview profile will notice a warning if they sign up with a email domain that is public (ex, gmail.com, 163.com, qq.com, etc.) or if the domain is not included in our institution list. The warning states that signing up with a public domain may spend up to 2 weeks in moderation. This warning has understandably triggered a large number of emails sent to the support address requesting an early activation. We see these emails, we may not answer each depending on the load, but we review moderation daily.

The warning was added by the staff in response to an increase in the number of fake/spam profiles being submitted with public domains, delaying moderation.

We encourage users to signup with their institutional (industry/government/university/research org) email domains to bypass moderation. "Institutional" in this case is defined as an established organization or corporation. If your domain is not recognized, please submit to moderation, we routinely add new domains to the list.

Forms are rendered in the UI using invitations. You can read more about invitations in the link below.

API V2 Invitations

You can report a bug or request a feature by going to our issue tracker repository. Before you do so, please read the guidelines so that we can understand and address your bug report or request. Once you are familiar with the procedure, you can make use of one of these templates to help us better understand your issue or feature request.

In order for a reviewer to see their assigned submissions, they need to be logged into an OpenReview account that has read permissions for the submission.

If a specific reviewer cannot access their assigned submission, they may need to check that the email they received the invitation to is added and confirmed to their account- The email should be listed in their profile with (Confirmed) next to it. If this is not the case, they should follow the steps to add an email to their account.

If all reviewers cannot access the forum page of their assigned submission, check that they are readers of the submission they are assigned to. On the Venue Request Form, make sure that the Submission Readers field includes reviewers. If reviewers are not listed as a reader, update the Post Submission stage to add them as readers for their submissions.

We've received many emails from concerned researchers who want to sign up quickly but aren't affiliated with an academic institution.

If you are not affiliated with an academic institution, but are employed at a company, you can use that domain and position information to sign up.

If you do not have a company domain, you can use a personal email. All personal emails will be moderated - see Expediting Profile Activation for additional tips on how to make sure your profile is activated as quickly as possible.

When filling out the profile details for registration, there is a section that will ask for your Education and Career History, which will require a current position. For the role you can type “Independent Researcher” and set that as your current position and type in a domain. See the page Entering Institutional Data for an example of how to fill out institutional information as an independent researcher. Please include as much of your background as possible. If the "Education and Career History" section only lists "Independent Researcher" we will ask you to add another institution record when your profile is rejected.

Please do not use an old role or affiliation as your current position, as that may delay moderation.

OpenReview requires every publication to have a license. If you have a paper that is under a license that is not listed, please contact us through the Feedback Form.

If you have lost access to your OpenReview account, please try the following steps.

1. Try resetting your password with alternate email accounts. You can reset your password with any email that was associated with it.

2. Contact OpenReview Support ([email protected]) from your new email with the following information: your old email or profile ID and any available documentation verifying your institutional history in order to gain assistance in resetting your password.

All submissions must be represented and submitted by human authors. There are no author profiles representing AI.

A field should be added to the submission form to indicate the content was generated by an LLM. Please see our guide on how to customize the forms.

Expertise Selection is a task for Program Committee members (such as reviewers) that gives them the opportunity to identify which previous publications they would like to be considered when being matched with submissions to review. If you want to use the same Expertise Selection configuration for multiple venues, it is possible to transfer the expertise from one venue to another using the OpenReview Python client using the following steps.

1.

2. Get Expertise Selection edges from the previous venue

OpenReview by default considers all publications as relevant expertise for paper matching and assignment. In Expertise Selection, edges are posted indicating the papers that should be excluded from paper matching. You can get the edges from a previous venue using the following method:

You will need the following information:

• profile_id: Your profile ID (such as ~First_Last1). Also see

• from_venue_id: The id of the venue you want to transfer expertise from. Also see:

• group_name: The name of the group you are in on the Program Committee (typically this is Reviewers or Area_Chairs)

The number of edges should correspond with the number of papers that you are excluding from Expertise Selection.

3. Copy edges to new venue

Finally, post an edge to the new venue that you are doing Expertise Selection for:

OpenReview’s goal is to provide scientific communication to the entire global community. Initially OpenReview was not available to users in Iran, Cuba, Syria, and several other countries because our cloud service provider blocked access as a simple approach to comply with United States economic sanctions and trade laws.

Recently the OpenReview staff has done extra work to make OpenReview available in all countries, including those above. In order to comply with relevant laws, OpenReview must guarantee that none of our registered users appear in the Office of Foreign Assets Control of the U.S. Department of the Treasury (OFAC) SDN list. We primarily accomplish this by looking for first-last-name matches in the list. When there is a name match, we ask for additional information that would disambiguate the OpenReview user from the person on the SDN list.

If you were notified that your profile has been limited, this means that the name on your profile matches that of a person on the SDN list. While in a limited state, you can log in to OpenReview, edit your profile, and view the same amount of data as before, but you will be unable to author any notes on the OpenReview system. This means you will be prevented from performing most common actions, including submitting to venues or posting reviews, meta-reviews, or comments. In order to reactivate your profile, you will need to do the following:

• Log in to OpenReview at https://openreview.net/login

• Navigate to your Profile at https://openreview.net/profile

• Click the Edit button.

• Find the field where you can enter your year of birth, and enter the information.

• Click Save at the bottom of the page.

OpenReview will routinely check for SDN matches, and if your birth year has been updated, your profile will return to active. Note that this change will not be immediate. If you believe you have been waiting longer than expected and your profile has not been reactivated, you can reach out to us using the .

If you don't want your profile to be publicly visible, you can uncheck the Profile Visibility setting from your Profile/Edit page. With this setting disabled, only authenticated (logged in) OpenReview users can view your profile.

1. Go to https://openreview.net/profile/edit

2. Click on "Personal Info"

3. Under "Profile Visibility", uncheck the box to hide your profile from the public

If your profile is public, unauthenticated individuals can see your:

• Name

• Personal Links

• Career & Education History

• Advisors, Relations & Conflicts (you can hide these items from your profile edit page)

You can see this by copying your profile link and opening it in an incognito browser.

I have a question about:

Throughout the course of a conference/workshop, members of the committee groups are assigned tasks to complete, such as, Expertise Selection, Reviewing, and the Reviewer License Agreement. Users can find their tasks by clicking on the Tasks button (openreview.net/tasks) on the red nav bar at the top of the page. They can also find these tasks in their respective venue consoles.

They'll see a list of different venue IDs and the number of pending and completed tasks.

To view the tasks, click on the arrow next to the venue ID or "Show pending tasks and completed tasks". Clicking on a task link will redirect the user to another page to complete the task. When the task is completed it will be grayed out on the Tasks page. When the expiration date for that task expires the task will disappear from the Tasks page.

The OpenReview system uses the reviewer's publications from Expertise Selection in order to match reviewers and papers via affinity scores. Reviewers who do not have existing publications should leave the Expertise Selection form blank, and the reviewer will not be assigned an affinity score for a paper.

Decisions on how to assign reviewers without affinity scores is at the discretion of the venue organizers. Please contact the venue organizers if you have further questions about how review assignment will work for a specific venue.

Note: There is no 'Submit' button for Expertise Selection, and the task will show in your pending queue (where you can make changes) until the task expires at which time the task will automatically leave the queue.

See also:

A vulnerability is a defect (bug) in the system that compromises the integrity of the application or its data. If you found one, please as soon as possible so that it can be fixed. Please do NOT post about the vulnerability elsewhere.

As the venue organizer, you can choose to hide specific submission fields from all submission readers. When a field is hidden, it becomes visible only to the Program Chairs and to the paper authors.

Hide a field using Post Submission

If you want to restrict a submission's field visibility from everyone except the Program Chairs and the paper authors, you can do as follows:

1. From your venue request form, click .

There are a few common reasons why you might not have received the password reset email. You can try the following steps to debug the issue

1. Check that the email was not sent to a spam or junk folder.

2. Try sending the password reset email again and double check that there are no typos in the email.

There are a few different ways to find your venue id.

1. If you are a Program Chair, go to your and copy the information in the field Venue ID

2. Use the URL of the submission page. The venue id is the portion of the url after group?id:For example for ICLR 2024 the submission homepage is : , and the venue id is ICLR.cc/2024/Conference

Each venue decides its own policy for how to handle requests to change the authorship list, order, or author details after the deadline. This is sometimes listed on the venue website or FAQ. If you need to request a change to your submission after the submission deadline has passed, please contact the venue organizers.

You can try the following steps to debug issues related to adding your DBLP link to your profile:

1. Ensure that the DBLP link is properly formatted and uses the persistent URL (see for more details about persistent URLs)

2. Ensure that your DBLP link is a single author page. If the link has a banner that states that it is a "disambiguation page", or if the link contains publications that belong to another researcher (See this by DBLP for more information) there will be issues with importing papers. Please see the above warning about contacting DBLP with correct requests.

3. Check for previous profiles. Sometimes users have previously created profiles with DBLP links. If you get an error stating another user is using your profile, check for previous accounts using past emails.

4. Check for claimable profiles. There are some profiles that have been pre-created by OpenReview. You can go to the page and type the first and last name in the conflicting profile and check for claimable profiles.

5. Contact support. If none of the above steps work, please . Include your profile id, the DBLP link, and the error message you receive when you attempt to update your profile.