Grant per-trigger execution rights
Every manual trigger in heliana has its own permission key: trigger:exec:<trigger-id>. A member can only see and run a trigger if their role includes that specific key. This lets you scope who can run which manual trigger — kick vs. ban vs. broadcast — instead of an all-or-nothing “can run triggers” toggle.
How it works
Section titled “How it works”When you save a manual trigger, heliana automatically creates a trigger:exec:<id> permission key for it. The key appears as a row in the Trigger actions group of the roles matrix.
Owner and Admin can already run every manual trigger regardless of the matrix — they don’t need the key granted. Viewer and Clan leader are fixed roles too: their matrix cells are locked, shown with a lock icon, and can’t be checked. Only a custom role you create can be granted a specific trigger’s execution key.
Wherever a manual trigger’s Actions menu shows up — the player dialog for player-targeted triggers, or the server status widget on the Dashboard for server-targeted triggers — a trigger only appears for members whose role includes that trigger’s execution key (or who are Owner/Admin).
Grant access to a trigger
Section titled “Grant access to a trigger”- Create a custom role first if you don’t have one yet (see Roles & permissions).
- In the left sidebar, click Roles.
- Click Edit.
- Scroll down to the Trigger actions group. Each manual trigger you have created appears as a row labeled with the trigger’s name.
- Check the box in your custom role’s column for the trigger it should be able to run.
- Click Save.
Custom roles aren’t assignable to members yet
Section titled “Custom roles aren’t assignable to members yet”The Members table and the invite dialog only let you set a member’s role to Admin, Viewer, or Clan leader — a custom role can’t currently be assigned to a member through the UI. So while you can configure a custom role’s trigger execution keys in the matrix today, there’s no UI path yet to put a teammate into that role. In practice, trigger access today comes from being Owner or Admin.
Trigger actions group is hidden when no manual triggers exist
Section titled “Trigger actions group is hidden when no manual triggers exist”The Trigger actions group only appears in the matrix when at least one manual trigger exists. If you see no such group, create a manual trigger first.