> For the complete documentation index, see [llms.txt](https://docs.claimr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claimr.io/campaigns/leaderboard.md).
# Leaderboard
This section lets you set up a public leaderboard to showcase top-performing participants in your campaign. It helps boost engagement by adding a competitive element.
To access these settings
1. Log in to your claimr account.
2. Select the **Campaign** you want to apply settings to.
3. Navigate to the campaign's **Settings** section.
4. Select **Leaderboard** from the settings menu.
To customize its settings, click the Edit (pencil) icon in the corner. This will open a settings window.
### Max. Entries
Define the maximum number of users to be displayed on the leaderboard. For example, setting this to 100 will show the top 100 participants.
### Page size
Set how many users are shown per page. This controls pagination and helps manage large leaderboards by breaking them into smaller chunks.
### Task dependencies
Select which tasks contribute to the leaderboard score. Only points earned from the selected tasks will be counted. This allows you to filter out low-effort or irrelevant tasks and focus the leaderboard on meaningful contributions.
---
# 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.claimr.io/campaigns/leaderboard.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.