> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/pro-system/rating-systems.md).
# Rating Systems
## Related Updates
* [Filter Customers by Rating](/pro-system/rating-systems/filter-customers-by-rating.md)
The PodPlay system allows for three types of ratings inside a Customer’s Profile:
* Custom Ratings
* DUPR Ratings (pickleball)
* WPR Ratings (padel)
## Custom Ratings
When a Club chooses to use **the Custom Ratings option**, any Admin can enter a numerical value inside the Customer’s Profile.
* This numerical value is a static value and does not change unless an Admin goes into the Customer’s Profile and changes the value.
## DUPR Ratings
To connect with the DUPR rating system:
* A Customer will click on the DUPR Rating button in the Account tab of the app
* Once the Customer has connected their DUPR account, the DUPR Rating button will show a “Live” flag
There are two aspects to the ranking system connection:
* First, the **Read** function allows PodPlay to connect with a DUPR account through Auth0
* It reads the DUPR account of the Customer and pulls their ranking or rating into their PodPlay account
* Second is the **Write** function, which will copy the **Scoreboard** results after a match or game and send it to the ranking system for historical accuracy
* If everyone in the match or game has a DUPR profile, PodPlay will be able to send the **Scoreboard** results to the DUPR system and automatically update the ratings of those players involved in the game
* If someone in the match or game does not have a DUPR account connected, the DUPR system will not know what to do with the information and will not record the results, so the **DUPR Challenge Match** will not be functional
An Admin can then set a required rating during the Event creation flow.
* They will set the rating requirements, which will mean that any Customer who does not meet the minimum rating will not be allowed to join the Event
* To learn more, read about [**Creating a DUPR Gated Event**](https://help.podplay.app/en/articles/2024257)
## WPR Ratings
World Padel Rating (WPR) works similarly to DUPR for **padel** venues:
* Customers connect a WPR account from the app; staff enable WPR under **Company Settings → Ratings**.
* When **Submit results to WPR** is enabled, finished rated padel matches can be sent to WPR automatically after scoreboard play.
* Staff can review linked **WPR IDs** and publication status in **Match Details** on the Matches dashboard or an Event’s **Matches** tab (when the matches feature is enabled for your club).
To configure WPR hosts, credentials, and submission toggles, use **Company Settings → Ratings**. For staff overrides on customer profiles, see [Club Rating Overrides](https://github.com/pingpod/pingpod-web-v2/tree/main/applications/docs/web-admin/users/club-rating-overrides.md).
## Hide Ratings
By default, Customers can turn off **Show rating on event attendees list** in their app preferences to keep their rating off Event attendee lists.
To require ratings on attendee lists, turn on **Disable Ability to Hide Ratings** under **Company Settings → Ratings → Hide Ratings**:
* Customers can no longer hide their rating. Mobile apps that still show the preference will stop showing it once they support this setting; until then, turning it off has no effect
* A Customer's rating always appears next to their name on the attendee list, even if they previously turned the preference off
* Customers who don't share their name on the attendee list stay anonymous, and the setting doesn't show their rating
---
# 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.podplay.app/pro-system/rating-systems.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.
