Manage exceptions
An exception lets a specific player through your synced ban lists — either across the whole organization or on a single server. Use one when a player matches a ban you imported from an outside source but you want to allow them anyway: a false positive, an old entry from another community, or someone you’ve cleared.
Exceptions live in the player’s Lists tab.
Add an exception
Section titled “Add an exception”- Open the player — from Players, or from a server’s live player panel on the Dashboard.
- Switch to the Lists tab.
- Scroll to the Exceptions section.
- Click the button. Its label depends on where you opened the player from:
- Allow on this server — the player is allowed on this one server, even if a synced ban list matches them.
- Allow org-wide — the player is allowed across every server in your organization.
- Confirm in the dialog that appears (Allow).
The exception shows up right away, with its scope (This server or Org-wide) and the date.
Remove an exception
Section titled “Remove an exception”In the Exceptions section, click Remove on the entry. The player is again subject to any synced ban list that matches them.
How exceptions behave
Section titled “How exceptions behave”- An exception doesn’t delete anything from the source list — it only tells heliana to let that player past a match.
- A This server exception only covers that one server. Other servers still enforce the ban.
- If you later remove or re-point the ban list that matched them, the exception simply stops mattering; it isn’t cleaned up on its own.
Who can do what
Section titled “Who can do what”| Action | What it needs |
|---|---|
| See the exceptions on a player | Ban lists: Read (banList:read) |
| Add or remove an exception | Bans: Delete (ban:delete) |
Add and remove deliberately need the same permission as lifting a ban — so a role that can manage lists can’t quietly clear players it shouldn’t. See Roles & permissions.