> For the complete documentation index, see [llms.txt](https://docs.invitelogger.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.invitelogger.me/premium/features/smartleaderboard.md).
# SmartLeaderboard
Get a fixed leaderboard refreshed every 15 minutes automatically in one of your server channel⭐
This feature allow your members to **check their invite count** without doing any commands, useful for invites contest.
To setup it just run the **`/smartleaderboard send`** command
### The check invites button:
An alternative way for user to check their invites
### Invite generation system
This system allow the users to easily get their **own invite link** to share with their friends through a button below the smartLeaderboard. \
It also generate **expiring links** only that will avoid the struggle of reaching the 1000 invites code per server limit. \
➡️*When using this feature, you should remove the `Create Invite` permission from your server member*\
\
This feature can be toggled though the **`/smartleaderboard list`** command by clicking on the `🔗` button
{% tabs %}
{% tab title="The button" %}
{% endtab %}
{% tab title="The message" %}
{% endtab %}
{% endtabs %}
---
# 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.invitelogger.me/premium/features/smartleaderboard.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.
