Bans
Block a key, a machine, an address or an account so that it cannot come back, even with a new key.
Open it now:Bans
How a ban matches
A sign-in is refused when any one of its identities matches an active ban of that application: the license key, the hardware ID of the machine, or the IP address. This is deliberate. A ban on a key also covers the machine it ran on, so the same person with a fresh key on the same PC is refused too.
Add a ban
Press Add ban on this page, or use the plus menu in the top bar. Paste any one of the following; Atlas detects which it is:
| You paste | What is banned |
|---|---|
| A license key | The key, plus every hardware ID and IP address it has used, and the hardware fingerprints stored for that machine. |
| A hardware ID | That machine. It cannot sign in under any license. |
| An IP address | Every client coming from that address. |
| A username | The account, and every hardware ID and IP address it has touched. |
| An email address | The matching account, with the same reach as a username. |
Add a reason; it is recorded and shown in the list. Bans made here do not expire. A ban takes effect on the next sign-in attempt, and sessions already open can be ended from Monitor, with Kill and ban license doing both in one step.
A key can also be banned from its row on Users. Cascade ban there also bans every other key and account that shares its hardware ID or IP address.
Read the list
The strip at the top counts bans by what they target: Total, Account, License, HWID and IP. Click one to filter. The list has a column for each identity, the device and the build it came from, the reason, when it expires (blank means never) and how long ago it was made.
| Filter | Values |
|---|---|
| Target | All, Account, License, HWID, IP |
| Type | Manual (you), System, Cascade, Auto (made by an alert rule) |
| Status | All, Active, Expired |
| Search | Matches the key, username, email, hardware ID, IP and reason |
Click a row for its details: the target, why, who and when, the log entry that triggered it when there is one, and the other bans on the same hardware or address. Copy selected as CSV copies the selected bans for a spreadsheet.
Lift a ban
Choose Unban on a row. The row disappears and an Undo button stays for 6 seconds; after that the ban is removed. To lift several, tick them and use Revoke. Lifting bans through the dashboard keeps the audit trail, so use it instead of editing the database.
What the customer sees
A banned customer gets the banned message. You can change its wording, and the wording for temporary bans and hardware bans, in Settings, Messages.
Bans also come from inside the program. A client that detects tampering reports it and Atlas bans the license and hardware; see What Atlas checks, and when.
Permissions
Viewing, adding and removing bans are three separate permissions (View, Add, Remove), so a reseller can be allowed to ban but not to lift.