Ban a player

You ban a player by running the Ban player trigger against them. It’s a manual trigger — heliana ships it pre-seeded in every organization, but disabled. The ban’s duration and scope (all servers, or one server) are set in the trigger’s own configuration; the only thing you type when you run it is the reason.

Turn on the Ban player trigger

Every new org already has the trigger — you enable it once.

1. Open Triggers.
2. Find Ban player in the list. It’s a manual trigger and starts disabled.
3. Flip its Enabled toggle on.

To see or change what it does — how long the ban lasts, whether it hits all servers or one — open the trigger and edit its ban action. See below for handling more than one length.

Ban a player

1. Open the player. Either go to Players and click them, or find them in a server’s live player panel on the Dashboard.
2. Click the Actions button.
3. Pick Ban player from the menu.
4. A dialog opens, titled after the trigger. Fill in reason — why you’re banning them (required).
5. If the trigger is scoped to a single server and heliana doesn’t already know which one, a Server picker appears — choose the server.
6. Click Run.

The ban is recorded right away. If you also fire an RCON kick — in the same trigger or a separate one — the player is booted; the ban record is written either way.

The Actions menu only lists manual triggers you can run that apply to a player. If you don’t see Ban player, check it’s enabled and that your role can run it.

Handle more than one ban length or scope

A single Ban player trigger carries one duration and one scope. If you regularly hand out, say, a 24-hour ban and a permanent one, make a copy:

1. In Triggers, duplicate the Ban player trigger.
2. Open the copy, rename it (e.g. Ban player — 24h), and edit its ban action’s duration and scope.
3. Enable it.

Both now show up in the player Actions menu, and you pick the right one at ban time.

View and lift a ban

Bans live in the player’s Lists tab.

1. Open the player and switch to the Lists tab.
2. Scroll to the Bans section. Each ban shows:
   • A status badge — Active, Expired, or Revoked.
   • The reason.
   • A meta line: the duration (until a date, or permanent), the scope (a server name or All servers), who issued it, and the date.
3. To lift a ban that’s still in effect, click Unban on the entry. For one that’s already lapsed, the control reads Revoke.

Lifting a ban needs the Bans: Delete permission (ban:delete). The record stays in the player’s history, marked Revoked.

Who can do what

Action	What it needs
Run the Ban player trigger	Permission to run that trigger (granted per-trigger on the Roles screen)
Unban / revoke	Bans: Delete (ban:delete)

See Roles & permissions to set who holds these.

See also

• Ban federation model
• Sync an external ban source
• Manage exceptions
• Roles & permissions