> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dapp.ing/llms.txt
> Use this file to discover all available pages before exploring further.
# Run community boards
> Publish a leaderboard of the builders around your ecosystem, choose what it rewards, and let the published rules do the trust work.
A community board recognizes the people building around you without anyone suspecting you picked them. You choose what it rewards, Dapping computes it, and the board publishes its own rules on your hub's **Community** tab.
## Two boards for two kinds of community
* **Contributors** ranks verifiable work: attested participation in your campaigns, credited products, verified roles, and tenure in your ecosystem, plus season-scoped engagement such as reviews, comments, upvotes, and tagged GitHub repositories. The season view is a rolling window over the length you choose, so older activity ages out; the all-time view does not.
* **Advocates** ranks recent visibility over a short rolling window: posts on X and articles on Dev.to that match the terms you track. It rewards the people talking about your ecosystem right now.
Membership is one click on the builder side: anyone who lists your company as one of their ecosystems joins the board, subject to the floor and ceiling you set, and anyone can decline being ranked without leaving.
## What you configure
Boards need the **Company** plan; owners and admins configure them. From **Settings**, then **Community**, you choose which boards run, which signal families count and how much XP each is worth, the season length, the terms the Advocates board tracks, the board's name and description, custom level names, and an optional link to where you announce rewards. You can grant bonus XP to a member with a written reason, and remove XP with a reason too; a removal counts in full against the season and, all-time, can only take back XP your company granted. Both appear in the member's breakdown with the reason attached.
## What the tracked terms actually reach
Each term is one of six types, and the type decides which board reads it and which platform is searched.
| You track | Type | Reads | Board |
| --------------------------------------------- | ----------------------------------------------- | --------------- | ------------ |
| An X handle, keyword, hashtag, or link domain | `x_handle`, `keyword`, `hashtag`, `link_domain` | X posts | Advocates |
| A Dev.to tag | `devto_tag` | Dev.to articles | Advocates |
| A GitHub repository topic | `github_topic` | Public repos | Contributors |
Each source is read once a day, and a member appears in one only if they have connected and verified that account. Somebody with no X connection cannot rank on posts however much they post.
Three exclusions are worth telling your community, because nobody guesses them: **reposts never count**, only original posts, quotes, and replies; **forks never count**; and a repository counts only for the member whose verified login owns it, so an org-owned repo credits nobody. Every X match is re-checked against your exact term, so a fuzzy search hit cannot slip through.
The GitHub topic is the one to publicize. Ask your ecosystem to tag repositories with it and Contributors starts reflecting real work within a day.
Campaigns plug in through [participation attestations](/for-companies/attest-participation-at-scale): set XP amounts on an import and everyone in that batch is credited on the board when you publish it.
## The constraint is the product
A leaderboard whose operator can quietly move an individual is a leaderboard nobody competes on. One where every hand on it is visible is a trust asset, and it is why your standings are worth announcing rewards against.
Scoring curves, level thresholds, ranking order, and the daily recompute are identical on every board. Membership follows the builders' own choice, shaped only by the floor and ceiling you set, both published on the board. No score can be edited directly and no ranking reordered by hand; bonus XP is the only lever over an individual, always reasoned, shown in their breakdown, and notified. The entitlement is enforced on the server, not in the browser.
Start with the signal families that match how your community contributes, and let a season or two run before tuning budgets. Use XP removal sparingly, with reasons you would defend in public.
## Continue on Dapping
Open your company hub's Settings, then Community, to enable and configure your boards.
## Related guides
Credit whole campaigns onto the board through attestations.
The board experience from your community members' side.
What a plan does and does not move, board standing included.
## What you configure
Boards need the **Company** plan; owners and admins configure them. From **Settings**, then **Community**, you choose which boards run, which signal families count and how much XP each is worth, the season length, the terms the Advocates board tracks, the board's name and description, custom level names, and an optional link to where you announce rewards. You can grant bonus XP to a member with a written reason, and remove XP with a reason too; a removal counts in full against the season and, all-time, can only take back XP your company granted. Both appear in the member's breakdown with the reason attached.
## What the tracked terms actually reach
Each term is one of six types, and the type decides which board reads it and which platform is searched.
| You track | Type | Reads | Board |
| --------------------------------------------- | ----------------------------------------------- | --------------- | ------------ |
| An X handle, keyword, hashtag, or link domain | `x_handle`, `keyword`, `hashtag`, `link_domain` | X posts | Advocates |
| A Dev.to tag | `devto_tag` | Dev.to articles | Advocates |
| A GitHub repository topic | `github_topic` | Public repos | Contributors |
Each source is read once a day, and a member appears in one only if they have connected and verified that account. Somebody with no X connection cannot rank on posts however much they post.
Three exclusions are worth telling your community, because nobody guesses them: **reposts never count**, only original posts, quotes, and replies; **forks never count**; and a repository counts only for the member whose verified login owns it, so an org-owned repo credits nobody. Every X match is re-checked against your exact term, so a fuzzy search hit cannot slip through.
The GitHub topic is the one to publicize. Ask your ecosystem to tag repositories with it and Contributors starts reflecting real work within a day.
Campaigns plug in through [participation attestations](/for-companies/attest-participation-at-scale): set XP amounts on an import and everyone in that batch is credited on the board when you publish it.
## The constraint is the product
A leaderboard whose operator can quietly move an individual is a leaderboard nobody competes on. One where every hand on it is visible is a trust asset, and it is why your standings are worth announcing rewards against.
Scoring curves, level thresholds, ranking order, and the daily recompute are identical on every board. Membership follows the builders' own choice, shaped only by the floor and ceiling you set, both published on the board. No score can be edited directly and no ranking reordered by hand; bonus XP is the only lever over an individual, always reasoned, shown in their breakdown, and notified. The entitlement is enforced on the server, not in the browser.
Start with the signal families that match how your community contributes, and let a season or two run before tuning budgets. Use XP removal sparingly, with reasons you would defend in public.
## Continue on Dapping