Integrations
Org-wide outbound integrations (Jira, PagerDuty, Teams) used by SOAR playbook actions like create_ticket and notify. ADMIN only.
/integrations
Configuring outbound integrations
OverviewIntegrations
This page configures the credentials SOAR playbook actions use to reach outside GuardFox — filing a Jira ticket, paging on-call via PagerDuty, or posting to a Teams channel. Split out of the personal Settings page since these apply platform-wide for the whole org, not just the signed-in user.
| Integration | What it's used for |
|---|---|
| Jira Service Desk | create_ticket SOAR action files an issue in the configured Jira project |
| PagerDuty | page_oncall SOAR action triggers an incident via the Events API v2 |
| Microsoft Teams | notify_teams SOAR action posts to the configured incoming webhook |
Values are stored in the AppSetting table; secrets (API token, integration key) are never echoed back to the browser after saving — the field shows a masked placeholder instead. Every save is recorded in the audit log as integrations.update.
This page requires the ADMIN role — a MANAGER or ANALYST won't see it in the sidebar and the underlying API rejects non-ADMIN requests server-side.