Cross-community ban visibility
heliana matches a player against ban lists kept by other heliana communities and treats a match as an advisory signal. It’s automatic — there’s nothing to set up, no partner org to add, and no consent step. Every community sees every other community’s matches.
How it works
Section titled “How it works”When heliana looks at a player, it checks their identities against ban lists maintained across all heliana organizations, not just your own. The match runs on every identity a player has — Steam, EOS, BattlEye, Mojang — so a ban in another community follows the person, not one single ID.
A match is purely informational. It’s read-only:
- It does not ban the player on your servers.
- It does not get shared or granted by anyone — visibility is on for everyone by default.
- You can’t turn it off, and you can’t share into it or opt out of it.
Think of it as background context on who a player is elsewhere, so you can make your own call. If you want a player actually blocked on your servers, ban them yourself (Ban a player) or import a source into one of your ban lists (Sync an external ban source).
There is no org-to-org sharing to configure
Section titled “There is no org-to-org sharing to configure”Earlier versions had an explicit “share my ban list with org X” / “subscribe to org X” flow. That’s gone. You don’t grant, revoke, or subscribe — cross-community visibility is the automatic signal described above. To bring outside bans onto your own servers, use a synced ban source instead.