Punishments and Appeals
Decide what happens to members who never verify or who fail too many times.
Punishments clear out the accounts that join, never verify, and sit in your member list forever. You choose what triggers the action, what the action is, and whether the member gets a way back in.
Access the Web Dashboard
Open your Tickety Dashboard. Log in using your Discord Account.
Navigate to Punishment Settings
-
Once logged in, locate and click on the "Configuration" section in the sidebar under the VERIFICATION category.
-
Open the Punishment Settings section on the Verification Configuration page.
Turning punishments on
- Punishments - Turns automatic action on for members who never verify in time or who fail too often. Every other field in this section appears once it is on.
You also need a trigger. Saving fails with "Set a grace period or a max failed attempts value to enable punishments" while both Grace Period and Max Failed Attempts are 0. Set one of them, or both.
Nothing runs while the Verification System toggle is off.
The two triggers
- Grace Period - How long a member has, counted from the moment they join, before the action runs if they are still unverified. Up to 1 year.
- Max Failed Attempts - Runs the action as soon as a member has failed this many verification attempts on the same link. Anything from 0 to 50, where 0 means no limit.
The grace period waits while a verification is actually in progress, so a member halfway through a captcha is not punished mid attempt. It is cancelled the moment they pass, and /force verify cancels it too.
Reaching the failed attempt limit also ends that attempt as failed, so the member has to press Verify again for a new link before they can try anything else.
Choosing an action
- Kick - Kick the user from the server. They can rejoin and start again.
- Ban - Ban the user from the server. Nothing short of an unban lets them back.
- Role Actions - Add or remove roles from the unverified user. Permanent: the roles stay as they are even if the member verifies later.
- Quarantine - Apply the roles, then let the user appeal it in a ticket. The only reversible role action.
Kick is the default. Pick Ban only if you are certain about your triggers, since a member who was simply away for a week is banned the same as a bot.
Reason
- Reason - The reason shown when the action is applied, up to 500 characters. It appears for Kick, Ban and Quarantine, and quarantined members also read it in their appeal message.
Left empty, Tickety writes its own reason describing whether the grace period ran out or the attempt limit was reached.
Punishment Roles
Shown for Role Actions and Quarantine. You build two rows: roles to add, and roles to remove.
| Free | Premium | |
|---|---|---|
| Roles added per punishment | 1 | up to 25 |
| Roles removed per punishment | 1 | up to 25 |
Extra roles above the free cap stay saved and start working again when premium returns. The picker refuses any role that sits above Tickety's own role.
Quarantine only takes back the roles it added. Roles it removed are not handed back when the member verifies, because nothing records whether they held them in the first place.
Quarantine and appeals
Quarantine applies the roles, then sends the member a direct message titled You Have Been Quarantined with your reason and, when you offer one, an Appeal This button.
- Appeal Panel - The ticket panel an appeal opens on. Leave it empty to quarantine without offering an appeal at all.
Pressing Appeal This opens an ordinary ticket on that panel, and the member is told Appeal Opened. Your staff answer it like any other ticket.
The button is only offered while the panel still exists and is enabled. If you delete or disable it, quarantined members are told appeals are closed and pointed back to your staff team. Switching to another punishment action clears the field for you.
What staff see in the appeal
Every appeal ticket opens with a Verification History card, so whoever picks it up has the story before they decide:
| Field | What it shows |
|---|---|
| What Happened | Never started, ran out of time, hit the attempt limit, was stopped by web security, or did not pass |
| Failed Attempts | How many attempts failed |
| Last Attempt | When the last attempt was |
| Detected | What was flagged on the attempt, when there was anything |
| Country | Where the attempt connected from |
| Threat Score | The score the attempt ended on |
The member gets their roles back by verifying normally: the roles quarantine added come off automatically as soon as they pass. Staff can also finish it by hand with /force verify.
Undoing a punishment by hand
/force verifymarks the member as verified, swaps their roles and cancels anything still pending against them./force unverifyreverses a verification. It does not remove quarantine roles and it does not restart a grace period.
Both need Manage Server or your admin role. See Verification Methods for the full command reference.
Setting it up in Discord
/configurator can set the punishment action, the grace period, the reason, the roles to add and remove, and the max failed attempts without opening the dashboard. It offers None, Kick, Ban and Roles only: Quarantine and the Appeal Panel are dashboard settings.
Where to go next
- Verification: the roles, messages, logging and the panel itself.
- Verification Methods: the three ways to verify, and the manual commands.
- Web Security: extra checks on browser verification, for premium servers.
- Ticket Logs: where appeal tickets show up alongside the rest.