Player actions as triggers

Manual triggers are buttons an admin clicks. Depending on how they’re set up, they appear in one of two places:

• Player-targeted — in the Actions dropdown on a player’s profile dialog. Use these for per-player actions: banning, warning, kicking, or a custom RCON command aimed at one player.
• Server-targeted — in the Actions dropdown on a server’s Server status panel. Use these for server-wide actions: broadcasts, map changes, ending a match.

A manual trigger you build from scratch is player-targeted. Server-targeted triggers come from the ready-made server triggers your organization ships with — Broadcast, Change map, End match, Run RCON command, Force seed bots — which you enable and edit. See Trigger templates.

This guide covers creating and granting access to player-targeted actions.

Create a player action

1. Navigate to your server, then open the Triggers tab.
2. Click New trigger. An empty trigger builder opens.
3. Set Type to Manual.
4. In the Name field, enter a name — this is the label admins see in the Actions menu.
5. Under Inputs, define any values the admin fills in at run time. Click Add input and set:
   • name — the input’s name, referenced in action fields as {input.name} (lowercased, with spaces replaced by underscores).
   • type — Text, Number, or Option.
   • Check req to make the input required.
6. Under Then, add the actions. Player values are available in RCON commands and other action fields: {player.name}, {player.steamID}, {player.eosID}. See Trigger actions reference.
7. Under Servers, choose All servers or a specific server.
8. Click Save.

The action now appears in a player’s Actions menu for any admin who has permission to run it.

Start from a ready-made trigger instead

Your organization ships with player triggers already seeded, switched Off: Ban player, Warn player, Kick player, Force team change, and Remove from squad. They’re pre-built for the player profile with the right actions and inputs. Open one, switch Enabled to On, edit if you want, and grant the run permission below.

How the run flow works

• Trigger with no inputs — clicking it in the Actions menu runs it immediately. A toast confirms success or failure.
• Trigger with inputs — clicking it opens a small dialog where the admin fills in the inputs, then clicks Run to execute.

Grant access to a player action

Each manual trigger has its own permission. Only admins whose role includes it see the trigger in the Actions menu.

The permission is created automatically when you save the trigger. The form shows this note under Permission: A dedicated permission is created for this trigger. Grant it to roles under Settings → Roles → “Trigger actions”; only members with it see the button.

To grant access:

1. In the left sidebar, under Organization, open Roles.
2. Click Edit.
3. Scroll to the Trigger actions group. Each manual trigger appears as a row labeled with the trigger’s name.
4. Check the box for the role that should be able to run this trigger.
5. Click Save.

Owner and Admin roles can run any manual trigger without this check. The Trigger actions group only appears once at least one manual trigger exists.

Where actions appear

Trigger	Where it shows up
Player-targeted	Actions dropdown on the player’s profile dialog
Server-targeted	Actions dropdown on the Server status panel

See also

• Per-trigger rights
• Roles and permission keys reference
• Trigger actions reference
• Trigger templates