Next steps

At this point you have a connected server, a live event feed, and at least one automated automation running. Here is what to tackle next.

Invite your moderation team

If you run your server with other admins or moderators, add them to your organization so they can use the dashboard without sharing your credentials.

• Invite admins — invite teammates by Discord username and assign roles.
• Roles & permissions — configure what each role can see and do across your servers.

Tag and watch players of interest

A player’s profile is where you add them to an access list or a tag — the built-in way to tag regulars, mark known griefers, or keep an eye on someone. A seeded watch tag is ready to use out of the box, or create your own.

• Tag & watch players — add players to tags from their profile.
• Find and inspect a player — look up any player by name or identity, and review their notes, lists, and stats.

Set up bans

Bans issued through heliana are stored persistently and tied to a player’s identities — on a Squad server, that means their EOS ID and, when known, their Steam ID. Beyond banning players yourself, you can pull in bans from outside sources and see how a player is viewed by other communities.

• Ban a player
• Sync an external ban source — import bans from BattleMetrics or a remote ban file (a Community Ban List export works as one) on the Bans → Sources tab.
• Cross-community ban visibility — see matching bans from other heliana communities on a player’s profile automatically.

Expand your automation automation

Beyond the teamkill autoban you set up in the previous step, automations can cover most repetitive moderation tasks:

• Create an event automation — react to any log event: kills, teamkills, chat messages, round endings, player joins.
• Create a scheduled automation — run checks or RCON commands on a fixed interval or cron schedule.
• Build conditions — filter events using AND/OR conditions, regex matching, counters, and player attribute checks.
• Pause an automation — keep an automation silent for N seconds after each run, per whole automation or per player.

Learn the underlying concepts

• How heliana parses the Squad log — what events come from the log and what comes from RCON.
• What is an automation — the complete automation model: kinds, conditions, actions, counters, and the pause.