Introductions to Invitations
See also:
In OpenReview, invitations define the rules and permissions for creating or editing entities such as notes, groups, and edges. They act as templates that control who can perform specific actions, what content is expected, and how submissions are processed.
The vast majority of invitations will be created automatically at the appropriate point of the workflow, and you will interact with invitations via the UI and stages within to change settings.
Structure of Invitations
See the API Reference for a detailed description of each field of the invitation. The main fields that you will interact with are:
id
: A unique identifier (e.g.,ICLR.cc/2025/Conference/-/Area_Chair_Registration
)invitees
: Who is allowed to use the invitation (e.g. Area Chairs)signatures
: Who issued the invitation (typically a venue or program chair group)edit
: Defines the type of object that can be posted (e.g.,note
,edge
)reply
orcontent
: Schema specifying required fields, validation, and structurereaders
,writers
, andsignatures
constraints for resulting entities
Creating Invitations
The vast majority of invitations will be created automatically at the appropriate point of the workflow, and you will interact with invitations via the UI and stages within to change settings.
In some cases, you may need to create custom invitations to accommodate less commons workflow. In this case, see guidance for those specific stages, or the Custom Stage.
Editing invitations
Pre-created invitations: The vast majority of edits to invitations are made via the venue configuration form. To maintain consistency across the venue, the values in the venue configuration will overwrite any changes made directly to invitations. Examples: Hiding submission fields, releasing reviews
Custom Invitations: For custom invitations that are not configurable in the venue configuration form, you may need to make changes directly to those invitations. In those cases, changes can be made in the Invitation's page, found on your venue's group page: http://openreview.net/group/edit?id={venue_id}
Changes to per-paper invitations: If you need to make programmatic changes to per-paper invitations for many submissions, you may want to make these changes programmatically.
Deleting invitations
Rather than outright deleting invitations, we use the expiration date. Update the exp_date
field of the invitation to now or a past time (in ms time), which will stop any new posts from being made with the invitations. Example: Updating Submission Expiration.
Last updated
Was this helpful?