> 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/v1/how-to-guides/paper-matching-and-assignment/how-to-update-a-reviewers-custom-max-papers.md).

# How to Update Custom Max Papers for Reviewers or ACs

Reviewers have the option to submit a form requesting a custom number of papers to review. The range of this custom number is defined by the organizers of the venue. Reviewers can set this value during the recruitment period by submitting a form that creates a Note with the Invitation `<your_venue_id>/Reviewers/-/Recruitment`. When paper matching setup is run, this note is converted to an Edge with the Invitation `<your_venue_id>/Reviewers/-/Custom_Max_Papers`.

{% hint style="info" %}
Refer to the invitation for edge configuration. You can view the invitation by going to: `https://openreview.net/invitation/edit?id=venue_id/role_name/-/Custom_Max_Papers`
{% endhint %}

**To create a reviewers' Custom Max Papers after having run Paper Matching Setup, you can do the following:**

1. If you have not done so, you will need to [install and instantiate the openreview-py client](/v1/getting-started/using-the-api/installing-and-instantiating-the-python-client.md).
2. Create an Edge object with proper params as in the example below:

```python
# For Reviewers
client.post_edge(openreview.api.Edge(
    invitation='<your_venue_id>/Reviewers/-/Custom_Max_Papers',
    head='<your_venue_id>/Reviewers',
    tail='~Profile_ID1',
    signatures=['<your_venue_id>/Program_Chairs'],
    weight=2
))
```

```python
# For Area Chairs
client.post_edge(openreview.api.Edge(
    invitation='<your_venue_id>/Area_Chairs/-/Custom_Max_Papers',
    head='<your_venue_id>/Area_Chairs',
    tail='~Profile_ID1',
    signatures=['<your_venue_id>/Program_Chairs'],
    weight=2
))
```

Please make sure the tail value is the profile id of the user. To get the profile id you can use the following call:

```python
profile = openreview.tools.get_profile('role@icml.cc')
profile.id
```

**To change a reviewers' Custom Max Papers after having run Paper Matching Setup, you can do the following:**

1. If you have not done so, you will need to [install and instantiate the openreview-py client](/v1/getting-started/using-the-api/installing-and-instantiating-the-python-client.md).
2. Retrieve the custom max papers edge for the reviewer or area chair. This edge will have the invitation `<your_venue_id>/Reviewers/-/Custom_Max_Papers` or `<your_venue_id>/Area_Chairs/-/Custom_Max_Papers` and the user's profile ID as its tail, so you can retrieve it like so:

```python
# For Reviewers
edges = client.get_edges(
    invitation="<your_venue_id>/Reviewers/-/Custom_Max_Papers",
    tail="~User_One1"
)
custom_max_papers_edge = edges[0]
```

```python
# For ACs
edges = client.get_edges(
    invitation="<your_venue_id>/Area_Chairs/-/Custom_Max_Papers",
    tail="~User_One1"
)
custom_max_papers_edge = edges[0]
```

The edge has a "weight" field. This represents the custom amount of papers they have agreed to review. To change it, you can set it to the new desired number of papers and repost the Edge.

```python
custom_max_papers_edge.weight = 2
client.post_edge(custom_max_papers_edge)
```

Once the edge is posted, it will appear in the reviewer's or area chair's console as the following image:

<figure><img src="https://content.gitbook.com/content/omUYsrTOIuqg28MvptIH/blobs/FBqJ33iWSXCR7B8eQhA8/image.png" alt=""><figcaption><p>Reviewer Console</p></figcaption></figure>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openreview.net/v1/how-to-guides/paper-matching-and-assignment/how-to-update-a-reviewers-custom-max-papers.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.