Giveaways
Auditable eligibility, draws, claims, and rerolls.
Start here
Create and run a controlled giveaway
PulseOne → Dashboard → select your server → Modules → Giveaways
Choose the server → Modules → Giveaways.
Under Giveaways create a new entry. Enter the prize and its destination, then review Where and when.
Set start/end times, then use Eligibility to restrict who can enter.
Save the giveaway, test entries from both eligible and ineligible accounts, and verify the draw or claim outcome after it ends.
Practical example
Run a short giveaway in a private test channel to confirm the entry limits and winner selection before promoting a public event.
Before you begin
- Enable first: messages.
- Discord bot permissions for the operational slice: ViewChannel, SendMessages, EmbedLinks.
- Review staff roles and channel access in your server before using the feature.
Overview of the setup
Before you begin
Create a published announcement template and configure entry rules, prize, start/end times and allowed roles.
Configure
Run a private test giveaway and submit valid and invalid entries to verify eligibility.
Test and verify
Close the test, review the winner selection, claim window and reroll audit before using a public prize.
Features explained
What each feature does and what to check before publishing or installing the result.
Eligibility rules
Eligibility controls who may enter and prevents ineligible duplicate entries.
Scheduled draws and claims
Configure a draw and claim window; draw results are auditable rather than staff-picked.
Auditable rerolls
Use rerolls only through the recorded flow, keeping the original outcome and the reason for change.
If it still does not work
- Members cannot enter? Check the entry window and Eligibility configuration.
- No winner? Check the draw status, participant eligibility and any claim rules.
Troubleshooting and safety checks
- A member cannot enter? Inspect role, membership, time window and entry limits before rerunning a draw.
- If a capability is unavailable in the UI, check the module's current rollout/availability instead of assuming every roadmap item is live.