Skip to main content
Contributor ⭐️⭐️
Nov 2, 2026 11:49 AM UTC
New Idea

Feature Request for Role-Specific Leaderboard Widget

Related products:CC Gamification

1. Problem Statement

Currently, the leaderboard widget only supports a role-exclusion (blacklist) mechanism to filter out unwanted users or roles.

2. Why the Current Solution Fails

In our permission architecture, every user is automatically assigned a common base role (e.g., “Registered User”). Because this role is universal, it cannot be excluded without accidentally blocking all users from the leaderboard entirely. As a result, administrators cannot isolate or display specific target roles (such as “VIP Members,” “Staff,” or “Contributors”) on the leaderboard.

3. Proposed Solution

Update the leaderboard widget settings to include an inclusion-based (whitelist) role selector.

  • Desired Behavior: Allow administrators to explicitly select which specific role(s) should be displayed on the leaderboard (e.g., selecting only “Contributors” or “Premium Members”).

  • Alternative: Allow a multi-select toggle for "Include Selected Roles" vs. "Exclude Selected Roles" so admins have full flexibility.

4. Business / User Value

  • Flexibility: Enables community managers to spotlight specific user tiers (e.g., top creators, staff, or tier-based subscribers).

  • Accuracy: Resolves configuration blocks caused by universal baseline roles.

  • Better Engagement: Drives gamification by allowing targeted leaderboards for specific user segments.

4 replies

jvdc
Expert ⭐️
Nov 2, 2026 3:06 PM UTC

Hey have a look at this idea, it might already describe what you’re looking for:

https://communities.gainsight.com/ideas/community%2Dleaderboard%2Dconfig%2Dadd%2Dpossibility%2Dto%2Dinclude%2Da%2Duser%2Drole%2D28137

Translate
Contributor ⭐️⭐️
Nov 2, 2026 3:13 PM UTC

Thank you for the reply , above method will exclude potential users who had some other roles too. We do not want that to happen.

Translate
jvdc
Expert ⭐️
Nov 2, 2026 3:33 PM UTC

It is not as beautifully described as your post but it’s essentially requesting the same!

Translate