Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nudj.cx/llms.txt

Use this file to discover all available pages before exploring further.

The Advanced step of the reward studio exposes the long-tail config that most rewards don’t need — but when you need it, you need it.

​
autoRedeem

Toggle autoRedeem (#819, #957) for rewards that should claim themselves on earn — no member wallet interaction required. Typical uses:
  • XP / Points multipliers — activate immediately on earn, no manual claim.
  • Instant discount codes — emailed/displayed immediately.
  • Effect rewards (XP Boost, Points Boost) — only meaningful if auto-activated.
autoRedeem applies to Asset rewards only. Entry rewards always “redeem” at the giveaway draw.

​
Cross-community rewards

Use additionalCommunityIds (#914, #916) to scope a reward to multiple communities in the same org. Typical pattern:
  • Org runs three regional communities.
  • Core rewards (like VIP status upgrades) should work everywhere.
  • One reward, additionalCommunityIds = [allCommunityIds].
  • Members in any community can earn and redeem.
In the admin UI this appears as an “Additional Communities” multi-select on the reward’s Advanced tab.

​
RBAC gating

Different roles see different reward controls (#1816, #1864, #1865):
RoleCan see rewardCan editCan deleteCan gift
ViewerYes (read-only)NoNoNo
ModeratorYesNoNoNo
ManagerYesYesNoYes
AdminYesYesYesYes
SuperAdminYesYesYesYes
Edit pages wrap form content in a <ReadOnlyFieldset> so Viewers and Moderators see the reward’s current state but can’t modify it. See Roles & Permissions.

​
Supply limits

Every allocation has a supply limit (#1451) — an absolute cap on how many can ever be distributed.
  • Finite (N) — stops distributing when cap is hit.
  • Infinity — unlimited. Special handling added in #659, #643 so Infinity serialises correctly through the API and UI.
Pair supply limits with:
  • maxAssetsPerUser (#735) — per-member cap.
  • maxEntriesPerUser (#639) — per-member cap (Entry rewards).
  • Both default to sensible values for new rewards.

​
Draft rewards

Flag a reward as Draft (#2011). Draft rewards:
  • Don’t distribute, even if attached to a Live challenge.
  • Show in admin lists but hidden from the member app.
  • Useful for preparing a reward launch in parallel with other content.
Flip to Live when ready. Attached challenges pick up the reward on next distribution.

​
Manual distribution

Manual Distribution (#2011) takes a reward out of the auto-distribution pipeline. Members never earn it from challenges — admins must gift it manually via Reward Gifting. Use for:
  • Top-tier VIP rewards that need human judgment.
  • Compensation / apology rewards (case-by-case).
  • Event swag handed out in-person and recorded after.

​
Scheduled attachment to challenges

When attaching a reward to a challenge, you can set a scheduled attach time (#1223). The reward doesn’t appear on the challenge until that time — useful for:
  • Rolling out a reward on day 7 of a week-long challenge.
  • Surprise mid-campaign upgrades.
  • Staggered reveal drops.

​
Quick reference

SettingUse when
autoRedeemReward requires no member action
additionalCommunityIdsReward spans multiple communities
Manual DistributionOnly admin-gifted, never auto-earned
Draft flagPrepare in parallel, launch later
maxAssetsPerUserPrevent hoarding
supply = InfinityBadges / evergreen rewards with unlimited count
Scheduled attachmentDelayed rollout within an ongoing challenge