Yes. Every action your team takes through ScopliDrop is recorded automatically, on every plan, with more than 70 kinds of action covered. Each entry names the member who did it, what it touched, and when, whether they acted from the dashboard or from a Discord command.
Server Audit Log
Know Exactly Who Did What in Your Discord Giveaways
Every action your team takes on your Discord giveaways lands in one searchable record of who did it, when, and what changed. From launches to prize code reveals, the history is always there.
The server audit log is ScopliDrop's running record of every action your team takes on your Discord giveaways. Each entry shows who did it, what it touched, where it came from, and when. More than 70 kinds of actions are recorded automatically: giveaways created, edited, ended, extended, and rerolled, schedules and templates changed, prize codes revealed, currency granted, fraud flags cleared, and settings updated.
Actions are attributed to the person, not the surface. A giveaway ended with a Discord command is recorded under the member who ran it, the same as if they had used the dashboard, and anything ScopliDrop does on its own, like launching a scheduled giveaway, is marked as System.
Edits keep their receipts. Expand an entry and you see what changed, field by field, with before and after values for settings like dates, prizes, and winner counts. Filters narrow the log to one person, one kind of action, or one time range, so "who changed the end date last Tuesday" takes seconds to answer.
How the Server Audit Log Works
From an action anywhere to an answer in the log, with nothing to configure in between
- 1
Every action records itself
There is nothing to set up or switch on. From the day ScopliDrop joins your server, every team action lands in the log the moment it happens. The dashboard, a Discord command, and ScopliDrop's own automation all write to the same place. The audit log records more than 70 kinds of actions, across these areas:
Giveaways
Created, edited, deleted, ended early, extended, rerolled, or moved to another channel.
Scheduling & automation
Schedules and recurring series created, changed, paused, and every automatic launch.
Prize codes
Every import, release, and reveal. Whenever a code was decrypted, the log names who saw it.
Fraud moderation
Flags cleared, restored, or escalated, so every flag decision your team makes is on record.
Economy moderation
Currency granted, deducted, or reset, with the amount and the member it touched.
Participant data
CRM fields and values edited, contacts deleted, and every in-Discord member lookup.
Settings & branding
Server, activity, and economy settings, bot profiles, templates, and auctions.
Team permissions
Every grant change is itself an entry, so the trail covers who was given access, not just what they did with it.
Integrations
Connections added, updated, or removed, including custom bot tokens.
- 2
Entries name the person, not the surface
Each entry shows the member's Discord name and avatar, and a small source marker says where the action came from: Dashboard, Discord, or System. A giveaway ended with a Discord command is attributed to the member who ran the command, exactly as if they had pressed the button in the dashboard. When a scheduled giveaway launches on its own, the entry says System, so you can always tell automation from a person.
- 3
Filter the log down to your question
Search by username or Discord ID to follow one person. Narrow to one kind of action, from giveaway edits to failed launches. Pick a time range. The filters combine, and a counter shows how many events match, so "what did our new helper do this week" is one search away.
- 4
Expand an entry for before and after
Edits keep their receipts. Expand an entry and the changed fields appear with their values before and after, so you see that the end date moved from Friday to Sunday, not just that someone touched the giveaway. Bigger structures, like a giveaway's task list, are recorded simply as changed. Other entries carry their own context: which winners a reroll swapped out, how much currency was granted and to whom, which channel a giveaway moved to.
6 of 6 entries
When Who Action Resource Source 22m ago 
kaiWinners rerolled Discord Nitro (1 Year)Dashboard 3h ago 
mira_vFraud flag removed Steam Deck DropDashboard 9h ago SystemGiveaway launch blocked Weekly Nitro DropSystem 1d ago kaiGiveaway edited Steam Deck DropDiscord 2d ago mira_vServer settings updated Server settingsDashboard 4d ago SystemSchedule launched Friday Community DropSystem Sample entries. Click a row to expand what changed.
- 5
Failed & blocked says why nothing posted
Launches that never happened are recorded too, and the filter has a dedicated group for them. A Failed entry means something broke, most often the bot missing a permission in the target channel, and it shows the error. A Blocked entry means ScopliDrop refused on purpose, like a plan limit being reached or a linked prize pool running out of codes. The morning after a quiet launch night, this group is the first place to look.
Questions the Log Answers
Three situations where the record does the talking
Settle a reroll dispute with the record
A member insists they won and were swapped out unfairly. Filter to rerolls and open the entry. You get who rerolled, when, which kind of reroll it was, and which winners were swapped out. The conversation ends with a screenshot instead of a debate.
Answer "who saw this prize code"
A Steam key turns out redeemed before the winner ever touched it. Every decrypt of a pool code is an audit entry, whether it was a host reveal or a winner delivery. So the log holds the full list of everyone who ever saw that code. That trail is why prize pools and code delivery can promise winner-only codes in the first place.
Review a new helper's first week
You granted a new mod giveaway access through granular role permissions. A week later, search their name and read their trail: what they launched, what they edited, what they touched that surprised you. Trust builds faster when checking is this cheap.
The Other Half of Letting Your Team Run Giveaways
What a written history changes about running a giveaway team
Granular role permissions decide what your team can do. The audit log shows what they did. Together they make delegation work in both directions. You hand out access knowing every use of it leaves a trace, and your team works freely instead of reporting every routine action back to you.
It also settles questions before they become arguments. Most disputes in a giveaway server are not about what happened, they are about nobody being able to prove what happened. A record everyone can check ends those threads early, and your staff stop having to defend routine actions from memory.
Permission changes are recorded too, so the trail reaches back past the action itself. If someone was able to do something, the log also shows when they were given that access, and by whom.
Combine It With
The features whose actions the log keeps honest
Audit Log Questions
How far back it goes, who can read it, and how it differs from Discord's own log
Related Features
Granular Role Permissions
Give each Discord role exactly the dashboard access you want, no more.
Explore Granular Role PermissionsPrize Pools & Code Delivery
An encrypted prize code vault. Each winner gets a code reserved and revealed privately in their claim ticket.
Explore Prize Pools & Code DeliveryWho Did What, Always On Record
On every plan from day one. Add ScopliDrop, hand out access, and the history writes itself.